Summary: | pycups-1.9.46 fails with: '/usr/bin/python' isn't valid symlink | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | qeldroma <qeldroma> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | decibels.2862, zvasylvv |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
qeldroma
2009-09-24 17:34:55 UTC
(In reply to comment #0) > I checked the symlink, it's ok: > # ls -l /usr/bin/python* > lrwxrwxrwx 1 root root 9 24. Sep 18:51 /usr/bin/python -> python2.6 It's obviously incorrect. /usr/bin/python must be a symlink to python-wrapper. You should run e.g.: eselect python set python2.6 I got same error ('/usr/bin/python' isn't valid symlink) while tried to update a setuptools. IMHO this error does not depend on package. I guess it happens after user updated a python (ie 2.5->2.6). After emerge has been finished, some amount of recommendation is shown. One of them says that run of python-updater is highly required. Its sets /usr/bin/python symlink to /usr/bin/python2.6, while correct value is python-wrapper. Could maintainers of python check this test case? I saw this issue today as well, while upgrading a dev-python/pycrypto. I wish the error message was more, clear and maybe pointed me to `eselect` However, when I ran `eselect python list` it showed I had 2.6 selected lithium / # eselect python list Available python interpreters: [1] python2.4 [2] python2.6 * As a symlink to 2.6 not to python-wrapper lithium / # stat /usr/bin/python File: `/usr/bin/python' -> `python2.6' Then I simply re-selected 2.6 and all was well lithium / # eselect python set python2.6 lithium / # stat /usr/bin/python File: `/usr/bin/python' -> `python-wrapper' None of the updates (for python, pycrypto or eselect) told me to do this in their emerge/ebuild outputs. reselecting python 2.6 worked for me even though already had it selected and was the only one to select. Was emerging 'sip' when got this error. |