| Summary: | Ebuilds involving dev-python/gnome-applets-python fail due to sandbox violations | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robert Bradbury <robert.bradbury> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | pchrist |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info | ||
Created attachment 226143 [details]
emerge --info
Attempting to eselect alternate versions of python (e.g. 3.1 vs. 2.6) did not change the sandbox failure. The gnomeapplet.so file is in /usr/lib/python2.6/site-packages/gtk-2.0/gnomeapplet.so and re-emerging "gnome-applets-python" which updates that file had no effect.
Do you still suffer this with Gnome 2.30 and updated gnome-python packages? I never suffered this issue :-/ Good luck Please try with 2.30 |
Multiple ebuilds, e.g. gnome-extra/hamster-applet-2.28.2, gnome-base/gnome-applets-2.28.0 and gnome-extra/deskbar-applet-2.28.0 fail during ebuilds with a sandbox violation when attempting to import the python library "gnomeapplet". Reproducible: Always Steps to Reproduce: 1. Unmask package level in package.keywords (e.g. gnome-base/gnome-applets ~x86) 2. emerge gnome-applets (or one of the other packages cited). Actual Results: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE "/var/log/sandbox/sandbox-4805.log" VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: utime S: deny P: /home/bradbury/.tmpdir/orbit-bradbury A: /home/bradbury/.tmpdir/orbit-bradbury R: /home/bradbury/.tmpdir/orbit-bradbury C: /usr/bin/python2.6 -c import sys try: import gnomeapplet except ImportError: sys.exit(1) except: sys.exit(0) sys.exit(0) -------------------------------------------------------------------------------- Expected Results: Package should emerge properly. Changing /etc/make.conf (or ebuild environment) so one has FEATURES="-sandbox" appears to work around the problem and allow the packages to emerge properly.