1 |
Hi, |
2 |
|
3 |
I think I've got my gentoo installation all effed up. I went a few weeks |
4 |
without doing a --sync followed by a emerge -uD world. On top of that I, |
5 |
I installed my own version of Python 2.5.1 from the source tarball off |
6 |
of python.org. Now, after a --sync, when I do an emerge -uD world I will |
7 |
see ACCESS DENIED errors when unlink is called on *.pyc files. An |
8 |
example summary is given below. I searched the forums for similiar |
9 |
problems. Solutions that worked for other people involved re-emerging |
10 |
particular packages. I tried that and it didn't work for me. Can I fix |
11 |
this mess? Or is my system fubar? Any ideas? |
12 |
|
13 |
Why is unlink getting ACCESS DENIED errors when I run emerge as sudo? |
14 |
|
15 |
Thanks, |
16 |
Tom |
17 |
|
18 |
... |
19 |
>>> Source compiled. |
20 |
--------------------------- ACCESS VIOLATION SUMMARY |
21 |
--------------------------- |
22 |
LOG FILE = |
23 |
"/var/log/sandbox/sandbox-gnome-base_-_gnome-desktop-2.20.1-27301.log" |
24 |
|
25 |
unlink: /usr/share/xml2po/docbook.pyc |
26 |
unlink: /usr/share/xml2po/docbook.pyc |
27 |
unlink: /usr/share/xml2po/docbook.pyc |
28 |
unlink: /usr/share/xml2po/docbook.pyc |
29 |
unlink: /usr/share/xml2po/docbook.pyc |
30 |
unlink: /usr/share/xml2po/docbook.pyc |
31 |
unlink: /usr/share/xml2po/docbook.pyc |
32 |
unlink: /usr/share/xml2po/docbook.pyc |
33 |
unlink: /usr/share/xml2po/docbook.pyc |
34 |
unlink: /usr/share/xml2po/docbook.pyc |
35 |
-------------------------------------------------------------------------------- |
36 |
|
37 |
|
38 |
-- |
39 |
gentoo-user@g.o mailing list |