Gentoo Archives: gentoo-user

From: "Bo Ørsted Andresen" <bo.andresen@××××.dk>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] gnome-panel-2.14.2 ACCESS VIOLATION
Date: Mon, 25 Sep 2006 12:20:42
Message-Id: 200609251415.15935.bo.andresen@zlin.dk
In Reply to: [gentoo-user] gnome-panel-2.14.2 ACCESS VIOLATION by Helmut Jarausch
1 On Monday 25 September 2006 13:22, Helmut Jarausch wrote:
2 > I've found a strange thing.
3 >
4 > During an emerge --update --deep --newuse world
5 > I've got
6 >
7 > Leaving directory
8 > `/var/tmp/portage/gnome-panel-2.14.2/work/gnome-panel-2.14.2'
9 >
10 > >>> Source compiled.
11 >
12 > --------------------------- ACCESS VIOLATION SUMMARY
13 > --------------------------- LOG FILE =
14 > "/var/log/sandbox/sandbox-gnome-base_-_gnome-panel-2.14.2-13019.log"
15 >
16 > This file contains
17 >
18 > unlink: /usr/share/xml2po/docbook.pyc
19 >
20 > An ad hoc work around was to chmod /usr/share/xml2po to be
21 > world writeable
22 > which isn't the right solution.
23
24 You can say that again!
25
26 > Since this emerge was running as root the installation process seems
27 > to drop priviledges temporarily.
28
29 Not quite. [1] explains it better that I could... If you really wanted to
30 ignore a sandbox violation you should run:
31
32 # FEATURES=-sandbox emerge --oneshot gnome-panel
33
34 I wouldn't do that though...
35
36 > Am I missing something or is it a bug?
37
38 You are definitely missing something. Apparantly this is some kind of
39 regression of bug #104088 [2]. I guess the fix is in comment #8.
40
41 [1] http://bugday.gentoo.org/sandbox.html
42 [2] http://bugs.gentoo.org/show_bug.cgi?id=104088
43
44 --
45 Bo Andresen