Summary: | sys-apps/portage-2.1.7.17 /var/tmp/portage symlink triggers sandbox violation | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aaron Ten Clay <gentoo-bugzilla> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log from failed unpack |
Description
Aaron Ten Clay
2010-03-11 05:23:14 UTC
Created attachment 223111 [details]
Build log from failed unpack
build.log from failed merge when /var/tmp/portage is a symlink
This is due to fact that sandbox does not follow symlinks. Instead of using a symlink for /var/tmp/portage, you should override PORTAGE_TMPDIR in /etc/make.conf. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b414c49cec13202c34ea4115f79978ca7177acaf (In reply to comment #3) > This is fixed in git: > > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b414c49cec13202c34ea4115f79978ca7177acaf Actually, I've just noticed that I added a duplicate realpath call there, and that portage-2.1.7.17 already had a realpath call. So, now I'm not sure what triggered the sandbox violation. Are you still able to reproduce this problem? Please re-open if you can still reproduce this. No longer reproducible. Thanks :) |