1 |
On Tue, 21 Oct 2008 19:33:57 -0400 |
2 |
David Relson wrote: |
3 |
|
4 |
> I've just updated from python-2.5 to 2.6. Since emerge ran fine, I |
5 |
> ran python-updater. It's encountering problems with lots of |
6 |
> packages. For example, "emerge -1 setuptools" ends with: |
7 |
> |
8 |
> ########## begin emerge output ########## |
9 |
> |
10 |
> copying build/lib/pkg_resources.py |
11 |
> -> /usr/lib64/python2.6/site-packages ACCESS DENIED |
12 |
> open_wr: /usr/lib64/python2.6/site-packages/pkg_resources.py |
13 |
> error: /usr/lib64/python2.6/site-packages/pkg_resources.py: Permission |
14 |
> denied |
15 |
> * |
16 |
> * ERROR: dev-python/setuptools-0.6_rc8-r1 failed. |
17 |
> * Call stack: |
18 |
> * ebuild.sh, line 49: Called src_install |
19 |
> * environment, line 2445: Called distutils_src_install |
20 |
> * environment, line 724: Called die |
21 |
> * The specific snippet of code: |
22 |
> * ${python} setup.py install --root="${D}" --no-compile "$@" || die |
23 |
> "python setup.py install failed"; |
24 |
> * The die message: |
25 |
> * python setup.py install failed |
26 |
> * |
27 |
> * If you need support, post the topmost build error, and the call |
28 |
> stack if relevant. |
29 |
> * A complete build log is located at |
30 |
> '/var/log/portage/dev-python:setuptools-0.6_rc8-r1:20081021-133932.log'. |
31 |
> * The ebuild environment file is located at |
32 |
> '/var/tmp/portage/dev-python/setuptools-0.6_rc8-r1/temp/environment'. |
33 |
> * |
34 |
> --------------------------- ACCESS VIOLATION SUMMARY |
35 |
> --------------------------- LOG FILE = |
36 |
> "/var/log/sandbox/sandbox-32513.log" |
37 |
> |
38 |
> open_wr: /usr/lib64/python2.6/site-packages/pkg_resources.py |
39 |
> -------------------------------------------------------------------------------- |
40 |
> |
41 |
> >>> Failed to emerge dev-python/setuptools-0.6_rc8-r1, Log file: |
42 |
> |
43 |
> >>> '/var/log/portage/dev-python:setuptools-0.6_rc8-r1:20081021-133932.log' |
44 |
> |
45 |
> * GNU info directory index is up-to-date. |
46 |
> |
47 |
> ########## end emerge output ########## |
48 |
> |
49 |
> This looks like a permissions problem |
50 |
> in /usr/lib64/python2.6/site-packages/. I normally run emerge as |
51 |
> 'relson', but this time I ran emerge as 'root' -- so I don't think |
52 |
> it's a simple permissions problem. |
53 |
> |
54 |
> Has anybody else emerge python-2.6 and run python-updater? Any idea |
55 |
> of what I may be doing wrong? Is it time to head for bgo? |
56 |
> |
57 |
> Regards, |
58 |
> |
59 |
> David |
60 |
|
61 |
http://bugs.gentoo.org/show_bug.cgi?id=240149 identified the fix! |
62 |
|
63 |
When python2.6 was installed, the entry in /usr/bin was created: |
64 |
|
65 |
$$$ ls -l /usr/bin/python* |
66 |
|
67 |
lrwxrwxrwx 1 root root ... python -> //usr/bin/python2.6 |
68 |
lrwxrwxrwx 1 root root ... python2 -> python2.5 |
69 |
-rwxr-xr-x 1 root root ... python2.5 |
70 |
-rwxr-xr-x 1 root root ... python2.6 |
71 |
|
72 |
The "//" in the symlink causes the problem. The problem was fixed |
73 |
with the following commands: |
74 |
|
75 |
root@osage portage # eselect python list |
76 |
Available python interpreters: |
77 |
[1] python2.5 |
78 |
[2] python2.6 * |
79 |
root@osage portage # eselect python set 2 |
80 |
|
81 |
so /usr/bin now has |
82 |
|
83 |
lrwxrwxrwx 1 root root ... python -> /usr/bin/python2.6 |
84 |
|
85 |
(with a single slash) and all is good! |