On Tue, 21 Oct 2008 19:33:57 -0400
David Relson wrote:

> I've just updated from python-2.5 to 2.6.  Since emerge ran fine, I
> ran python-updater.  It's encountering problems with lots of
> packages.  For example, "emerge -1 setuptools" ends with:
> 
> ########## begin emerge output ##########
> 
> copying build/lib/pkg_resources.py
> -> /usr/lib64/python2.6/site-packages ACCESS DENIED
> open_wr:   /usr/lib64/python2.6/site-packages/pkg_resources.py
> error: /usr/lib64/python2.6/site-packages/pkg_resources.py: Permission
> denied
>  * 
>  * ERROR: dev-python/setuptools-0.6_rc8-r1 failed.
>  * Call stack:
>  * ebuild.sh, line   49:  Called src_install
>  * environment, line 2445:  Called distutils_src_install
>  * environment, line  724:  Called die
>  * The specific snippet of code:
>  * ${python} setup.py install --root="${D}" --no-compile "$@" || die
> "python setup.py install failed";
>  * The die message:
>  * python setup.py install failed
>  * 
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/log/portage/dev-python:setuptools-0.6_rc8-r1:20081021-133932.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/dev-python/setuptools-0.6_rc8-r1/temp/environment'.
>  * 
> --------------------------- ACCESS VIOLATION SUMMARY
> --------------------------- LOG FILE =
> "/var/log/sandbox/sandbox-32513.log"
> 
> open_wr:   /usr/lib64/python2.6/site-packages/pkg_resources.py
> --------------------------------------------------------------------------------
> 
> >>> Failed to emerge dev-python/setuptools-0.6_rc8-r1, Log file:
> 
> >>>  '/var/log/portage/dev-python:setuptools-0.6_rc8-r1:20081021-133932.log'
> 
>  * GNU info directory index is up-to-date.
> 
> ########## end emerge output ##########
> 
> This looks like a permissions problem
> in /usr/lib64/python2.6/site-packages/.  I normally run emerge as
> 'relson', but this time I ran emerge as 'root' -- so I don't think
> it's a simple permissions problem.
> 
> Has anybody else emerge python-2.6 and run python-updater?  Any idea
> of what I may be doing wrong?  Is it time to head for bgo?
> 
> Regards,
> 
> David

http://bugs.gentoo.org/show_bug.cgi?id=240149 identified the fix!

When python2.6 was installed, the entry in /usr/bin was created:

$$$ ls -l /usr/bin/python*

  lrwxrwxrwx  1 root root ... python -> //usr/bin/python2.6
  lrwxrwxrwx  1 root root ... python2 -> python2.5
  -rwxr-xr-x  1 root root ... python2.5
  -rwxr-xr-x  1 root root ... python2.6

The "//" in the symlink causes the problem.  The problem was fixed
with the following commands:

   [EMAIL PROTECTED] portage # eselect python list
   Available python interpreters:
     [1]   python2.5
     [2]   python2.6 *
   [EMAIL PROTECTED] portage # eselect python set 2

so /usr/bin now has 

  lrwxrwxrwx  1 root root ... python  -> /usr/bin/python2.6

(with a single slash) and all is good!




Reply via email to