Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git-annex-5.20150731: setup: /home/stackage/.local: permission denied #726

Closed
juhp opened this issue Aug 3, 2015 · 12 comments
Closed

git-annex-5.20150731: setup: /home/stackage/.local: permission denied #726

juhp opened this issue Aug 3, 2015 · 12 comments

Comments

@juhp
Copy link
Contributor

juhp commented Aug 3, 2015

Not quite sure what is happening but latest git-annex is failing with:

:
[512 of 512] Compiling Main             ( git-annex.hs, dist/build/git-annex/git-annex-tmp/Main.o )
Linking dist/build/git-annex/git-annex ...
Installing executable(s) in /home/stackage/work/builds/nightly/bin
setup: /home/stackage/.local: permission denied

cc Joey Hess id@joeyh.name

@peti
Copy link
Contributor

peti commented Nov 3, 2015

Does $HOME point to to a writable directory when those builds are run? In NixOS, we set

export HOME=$TEMPDIR

for this particular build. It would be great to make some progress with this issue; git-annex is an important package, and the version currently found in Stackage is quite old already.

@peti
Copy link
Contributor

peti commented Nov 3, 2015

Cc: @joeyh

@joeyh
Copy link
Contributor

joeyh commented Nov 3, 2015

I was able to replicate this with a ~/.config that was not writable. Will skip installing desktop autostart etc files in this case.

@peti
Copy link
Contributor

peti commented Nov 3, 2015

Also, git-annex-5.20150731 is broken in Stackage Nightly (on NixOS) because of the aws-0.13.0 update: http://hydra.cryp.to/build/1346530/log/raw. I suppose we have to (a) downgrade aws or (b) upgrade git-annex to avoid that issue.

@joeyh
Copy link
Contributor

joeyh commented Nov 3, 2015

Aside:

@peti as for NixOS, I think you would be better served building git-annex using its Makefile. There's an install target in there that respects DESTDIR in the usual way, and so you can get the whole FHS filesystem tree, including files in /etc and then use that for you package in whatever ways make sense for NixOS. That will get a higher level of integration for the git-annex webapp than the cabal install to temp dir approach currently is capable of.

@joeyh
Copy link
Contributor

joeyh commented Nov 3, 2015

The aws-0.13.0 update was dealt with in yesterday's release of git-annex.

Does something specific have to be done to make stackage nightly include a new version of git-annex? I had sorta assumed new versions would be added automatically when dependencies allowed.

@snoyberg
Copy link
Contributor

snoyberg commented Nov 3, 2015

@juhp put in an upper bound in a151596 due to this issue. I can remove that upper bound now that the issue has been resolved (can you confirm that the fix is on Hackage?).

@joeyh
Copy link
Contributor

joeyh commented Nov 3, 2015

The fix for the permission denied problem isn't on hackage yet. Did that problem somehow break normal uses of stack install? I don't see how it could..

@snoyberg
Copy link
Contributor

snoyberg commented Nov 3, 2015

It broke the Stackage build server itself. How long until the fix is on Hackage?

@joeyh
Copy link
Contributor

joeyh commented Nov 3, 2015

Ah, ok. That justifies an immediate point release I'll say. Uploaded 5.20151102.1 just now.

In future, is there some way I could be informed of git-annex related bugs in stackage? I did not see this until I was pinged.

@peti
Copy link
Contributor

peti commented Nov 3, 2015

@joeyh, you could add your Github nick to https://github.com/fpco/stackage/blob/master/build-constraints.yaml#L575 to ensure you'll be notified about open issues.

@snoyberg
Copy link
Contributor

snoyberg commented Dec 3, 2015

It looks like this upper bound has been resolved, closing.

@snoyberg snoyberg closed this as completed Dec 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants