Summary: | Setting PORT_LOGDIR triggers sandbox access violations | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Joshua Pettett <bugs.gentoo.devel> |
Component: | Sandbox | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
ffmpeg build log with PORT_LOGDIR set
lm_sensors build log with PORT_LOGDIR set |
Description
Joshua Pettett
2005-12-13 10:19:35 UTC
Ie, portage not adding that dir to SANDBOX_WRITE. Created attachment 74653 [details]
ffmpeg build log with PORT_LOGDIR set
This is a build log from attempting to re-emerge ffmpeg with PORT_LOGDIR set.
Note that this is only one example, other emerges fail in the same way.
These same ebuilds emerge fine with PORT_LOGDIR unset, but of course there's no
log to attach. :-)
Created attachment 74660 [details]
lm_sensors build log with PORT_LOGDIR set
This is just another example of an emerge that fails when, and only when,
PORT_LOGDIR is set.
Also, this was done after upgrading portage to 2.0.53 (still using
sandbox-1.2.17).
/usr/portage/eclass/flag-o-matic.eclass: line 408: /dev/stderr: Permission denied Apparently you don't have the correct version of flag-o-matic.eclass because when I build ffmpeg it gives the the above error (different line number), but without a sandbox violation due to addwrite "/dev/stderr" being in the correct version of the eclass. Do you have eclass in RSYNC_EXCLUDEFROM or something? Doh, emerge sync seems to have fixed it. Actually, it appears my previous sync was the day before the eclass was fixed, and I would have synced again except that I was trying to maintain a mostly unchanged state to diagnose and fix some other problems I was dealing with. Oh well, sorry for the trouble. |