commit a2c3f26426b435b090b19057d52ceec5364b19ed Author: Michał Górny <mgorny@gentoo.org> Date: Wed Nov 18 20:41:29 2015 +0100 python-utils-r1.eclass: Ban installation helpers in EAPIs < 5 Ban python_do* and python_new* helpers in EAPIs older than 5. We should ban them in python-any-r1 uses, actually but that would break dev-python/pypy* ebuilds as they are written now. breaks currently stable dev-lang/python-2.7 - this ebuild is EAPI=4 and uses said functions: * ERROR: dev-lang/python-2.7.10-r1::gentoo failed (install phase): * python_do* and python_new* helpers are banned in EAPIs older than 5. * * Call stack: * ebuild.sh, line 93: Called src_install * environment, line 4163: Called python_domodule 'epython.py' * environment, line 3337: Called die * The specific snippet of code: * die "python_do* and python_new* helpers are banned in EAPIs older than 5.";
My thinko. That was supposed to be '< 4'.
*** Bug 567088 has been marked as a duplicate of this bug. ***
I'm having the same install failure while attempting to update dev-lang/python-2.7.10-r1. If a fix has been distributed, it's probably being blocked by bug #567074 which I'm also seeing.
*** Bug 567106 has been marked as a duplicate of this bug. ***
*** Bug 567150 has been marked as a duplicate of this bug. ***
So, what's the fix, since Status is marked as "SOLVED FIXED" ?
(In reply to thanasis from comment #6) > So, what's the fix, since Status is marked as "SOLVED FIXED" ? You can look at the commit log for python-utils-r1.eclass to determine that.
Where do I find the commit log for python-utils-r1.eclass ?
(In reply to thanasis from comment #6) > So, what's the fix, since Status is marked as "SOLVED FIXED" ? rm -r /usr/portage/.git emerge --sync Most likely.
(In reply to thanasis from comment #8) > Where do I find the commit log for python-utils-r1.eclass ? In git. https://gitweb.gentoo.org/repo/gentoo.git/log/eclass/python-utils-r1.eclass
http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f359655316bd5d4e90fdb323502e7c972af28a7
*** Bug 570744 has been marked as a duplicate of this bug. ***