Attempt to install latest stable of portage, requires python-2.6 to be installed. The update from python-2.5 to python-2.6 fails with the following error message. >>> Emerging (6 of 7) dev-lang/python-2.6.4-r1 * python-gentoo-patches-2.6.4-r1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...[ ok ] * Python-2.6.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking python-gentoo-patches-2.6.4-r1.tar.bz2 to /var/tmp/portage/dev-lang/python-2.6.4-r1/work >>> Unpacking Python-2.6.4.tar.bz2 to /var/tmp/portage/dev-lang/python-2.6.4-r1/work >>> Source unpacked in /var/tmp/portage/dev-lang/python-2.6.4-r1/work >>> Configuring source in /var/tmp/portage/dev-lang/python-2.6.4-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-lang/python-2.6.4-r1/work ... >>> Source compiled. >>> Test phase [not enabled]: dev-lang/python-2.6.4-r1 >>> Install python-2.6.4-r1 into /var/tmp/portage/dev-lang/python-2.6.4-r1/image/ category dev-lang >>> Completed installing python-2.6.4-r1 into /var/tmp/portage/dev-lang/python-2.6.4-r1/image/ >>> Installing dev-lang/python-2.6.4-r1 !!! WARNING: Expected SLOT='2.6', got '' * * ERROR: dev-lang/python-2.5.2-r7 failed. * Call stack: * ebuild.sh, line 1827: Called die * The specific snippet of code: * die "error processing environment" * The die message: * error processing environment * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.5.2-r7/temp/build.log'. * The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.5.2-r7/temp/environment'. * !!! FAILED postrm: 1 * The 'postrm' phase of the 'dev-lang/python-2.5.2-r7' package has failed * with exit value 1. * * The problem occurred while executing the ebuild file named * 'python-2.5.2-r7.ebuild' located in the '/var/db/pkg/dev- * lang/python-2.5.2-r7' directory. If necessary, manually remove the * environment.bz2 file and/or the ebuild file located in that directory. * * Removal of the environment.bz2 file is preferred since it may allow the * removal phases to execute successfully. The ebuild will be sourced and * the eclasses from the current portage tree will be used when necessary. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm() * removal phases to be skipped entirely. After that emerge is no longer working: cheesey-desktop / # emerge --info cheesey-desktop / # Reproducible: Always Steps to Reproduce: 1. Update python-2.5 to python-2.6 2. 3. Expected Results: Update of python shall successfully be finished.
Please provide emerge --info.
(In reply to comment #1) > Please provide emerge --info. > Missed that it doesn't return anything for you. Where did you get this python-2.5.2-r7 ebuild? It's not in the tree.
The image I'm working on is for small touchscreen based terminals and wasn't updated for 1 - 2 years now. So that's why the current installed python is that old. Anyway, I would assume that upgrading from any python-2.5 should work, shouldn't it? I could also try to upgrade to a current python-2.5 first.
(In reply to comment #3) > The image I'm working on is for small touchscreen based terminals and wasn't > updated for 1 - 2 years now. So that's why the current installed python is that > old. > Anyway, I would assume that upgrading from any python-2.5 should work, > shouldn't it? I could also try to upgrade to a current python-2.5 first. > You could try that, assigning to maintainers anyway.
Post the output of: eselect python list ls /usr/bin/python*
# eselect python list Available Python interpreters: (none found) # ls -l /usr/bin/python* lrwxrwxrwx 1 root root 14 Feb 12 12:04 /usr/bin/python -> python-wrapper -rwxr-xr-x 1 root root 209 Feb 12 12:04 /usr/bin/python-config -rwxr-xr-x 1 root root 9480 May 21 16:45 /usr/bin/python-wrapper lrwxrwxrwx 1 root root 9 Feb 12 12:04 /usr/bin/python2 -> python2.5
*** This bug has been marked as a duplicate of bug 321145 ***
