Summary: | sys-apps/file-5.04 USE=python / distutils/python.eclass? - invalid atom: dev-lang/python:2.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Eclasses | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | python |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=5de77e44aa10ed5ff8262c184df651c2adc868bd | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
sys-apps:file-5.04:20101012-010219.log [x86~stable,fail]
environment file Patch to set EAPI=1 |
Description
Jeroen Roovers (RETIRED)
2010-10-12 01:42:49 UTC
Created attachment 250295 [details]
sys-apps:file-5.04:20101012-010219.log [x86~stable,fail]
Created attachment 250303 [details]
environment file
* environment, line 862: Called has_version 'dev-lang/python:2.6' That executes so in _python_final_sanity_checks(): if ! has_version "$(python_get_implementational_package)"; then die "$(python_get_implementational_package) is not installed"; fi; but it never dies, because python_get_implementational_package() which does: if [[ "$(_python_get_implementation "${PYTHON_ABI}")" == "CPython" ]]; then echo "dev-lang/python:${PYTHON_ABI}" [...] therefore assuming EAPI=1 while the ebuild has an implicit EAPI=0. Correct me if I'm wrong. It does look like it's just portage-2.2 that dies here, though: astrid /keeps/gentoo/local/app-portage/foobar # ebuild foobar-2.ebuild setup * Package: app-portage/foobar-2 * Repository: JeR * USE: elibc_glibc kernel_linux test userland_GNU x86 invalid atom: dev-lang/python:2.6 * ERROR: app-portage/foobar-2 failed: * unexpected portageq exit code: 2 * * Call stack: * ebuild.sh, line 56: Called pkg_setup * foobar-2.ebuild, line 9: Called has_version 'dev-lang/python:2.6' * ebuild.sh, line 198: Called die * The specific snippet of code: * die "unexpected portageq exit code: ${retval}" * * If you need support, post the output of 'emerge --info =app-portage/foobar-2', * the complete build log and the output of 'emerge -pqv =app-portage/foobar-2'. * This ebuild is from an overlay named 'JeR': '/keeps/gentoo/local/' * The complete build log is located at '/keeps/gentoo/emergelogs/astrid/app-portage:fo obar-2:20101012-022952.log'. * The ebuild environment file is located at '/var/tmp/portage/app-portage/foobar-2/tem p/die.env'. * S: '/var/tmp/portage/app-portage/foobar-2/work/foobar-2' astrid /keeps/gentoo/local/app-portage/foobar # cat foobar-2.ebuild # Copyright 1999-2010 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $ pkg_setup() { has_version dev-lang/python:2.6 } Created attachment 250309 [details, diff]
Patch to set EAPI=1
A simple and safe fix, although I think there's more to it than this.
(In reply to comment #3) > Correct me if I'm wrong. It does look like it's just portage-2.2 that dies > here, though: That's right, but it will be reduced to a eqawarn message in the next portage release. (In reply to comment #4) > Created an attachment (id=250309) [details] > Patch to set EAPI=1 > > A simple and safe fix, although I think there's more to it than this. That's the correct fix. There aren't many differences between EAPI 0 and 1, so there's not much that you need to account for: http://dev.gentoo.org/~zmedico/portage/doc/portage.html#package-ebuild-eapi-1 *** This bug has been marked as a duplicate of bug 340387 *** |