Bug 300579 – python.eclass: has_version() checks should be disabled for Python implementations

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Raúl Porcel (RETIRED) 2010-01-11 10:08:20 UTC]

>>> Installing (67 of 70) sys-devel/libtool-2.2.6b to /tmp/stage1root/
>>> >>> Emerging (68 of 70) dev-lang/python-2.6.4 for /tmp/stage1root/
>>> >>> Failed to emerge dev-lang/python-2.6.4 for /tmp/stage1root/, Log file:
>>> >>>  '/var/tmp/portage/dev-lang/python-2.6.4/temp/build.log'
 *
 * 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'.


Catalyst uses ROOT="/tmp/stage1tmp/" to create a stage1, its obviously then that python doesn't exist in that ROOT.

[Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2010-01-11 16:08:03 UTC]

Fixed.

[Comment 2 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2010-01-12 10:24:28 UTC]

*** Bug 300671 has been marked as a duplicate of this bug. ***

[Comment 3 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2010-01-12 10:24:36 UTC]

*** Bug 300678 has been marked as a duplicate of this bug. ***

[Comment 4 Raúl Porcel (RETIRED) 2010-01-16 12:22:19 UTC]

Now we get this:

 * 
 * 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'.
 * 

I can open a new bug if you want...

[Comment 5 Raúl Porcel (RETIRED) 2010-01-16 14:21:13 UTC]

Nvm, i see this was fixed.

Sorry :)