I have a computer that has been sitting around without being updated for 6 months and when trying to upgrade from python-2.5.4-r2 emerge fails with the following message: * ERROR: dev-lang/python-2.6.4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * python-2.6.4.ebuild, line 60: Called python_set_active_version '2.6' * python.eclass, line 200: Called die * The specific snippet of code: * die "${FUNCNAME}(): 'dev-lang/python:$1' isn't installed" * The die message: * python_set_active_version(): 'dev-lang/python:2.6' isn't installed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/python-2.6.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.6.4/temp/die.env'. * I managed to download an old python ebuild (2.6.2-r1) which i installed first and this solved my problems. Reproducible: Always Steps to Reproduce: 1. emerge -av --oneshot =dev-lang/python-2.6.4 2. 3.
Here i get, with same situation (2.5->2.6 upgrade): * * ERROR: dev-lang/python-2.6.4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * python-2.6.4.ebuild, line 68: Called has_version '=dev-lang/python-3*' * ebuild.sh, line 183: Called die * The specific snippet of code: * die "unexpected portageq exit code: ${retval}" * The die message: * unexpected portageq exit code: 127 * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/python-2.6.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.6.4/temp/die.env'. *
*** This bug has been marked as a duplicate of bug 300579 ***
