Created attachment 385594 [details] emerge --info dev-python/gconf-python Just another "failing duing compile instead of dependency resolution due to bad useflags" bug. * No Python implementation selected for the build. Please add one * of the following values to your PYTHON_TARGETS (in make.conf): * * python2_7 * ERROR: dev-python/gconf-python-2.28.1-r1::gentoo failed (configure phase): * No supported Python implementation in PYTHON_TARGETS. Easy fix: --- gconf-python-2.28.1-r1.ebuild 2014-09-27 21:44:35.870252863 +1200 +++ gconf-python-2.28.1-r1.ebuild 2014-09-27 21:37:19.579146812 +1200 @@ -19,5 +19,6 @@ >=gnome-base/gconf-2.11.1 !<dev-python/gnome-python-2.22.1" DEPEND="${RDEPEND}" +REQUIRED_USE="${PYTHON_REQUIRED_USE}" EXAMPLES=( examples/gconf/. )
REQUIRED_USE is already being set in gnome-python-common-r1.eclass :/
Hm. You do seem to be right. However, it appears missing from the md5-cached version of the file. DEFINED_PHASES=compile configure install postinst postrm preinst prepare test unpack DEPEND=dev-python/pygobject:2[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] >=gnome-base/gconf-2.11.1 !<dev-python/gnome-python-2.22.1 >=sys-apps/sed-4 ~dev-python/gnome-python-base-2.28.1 python_targets_python2_7? ( >=dev-lang/python-2.7.5-r2:2.7 ) dev-lang/python-exec:=[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] virtual/pkgconfig DESCRIPTION=Python bindings for the GConf library EAPI=5 HOMEPAGE=http://pygtk.org/ IUSE=examples python_targets_python2_7 KEYWORDS=alpha amd64 ~arm ia64 ~mips ppc ppc64 ~sh sparc x86 ~x86-fbsd ~x86-freebsd ~x86-interix ~amd64-linux ~x86-linux ~x86-solaris LICENSE=LGPL-2.1 RDEPEND=dev-python/pygobject:2[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] >=gnome-base/gconf-2.11.1 !<dev-python/gnome-python-2.22.1 ~dev-python/gnome-python-base-2.28.1 python_targets_python2_7? ( >=dev-lang/python-2.7.5-r2:2.7 ) dev-lang/python-exec:=[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] RESTRICT=test SLOT=2 SRC_URI=mirror://gnome/sources/gnome-python/2.28/gnome-python-2.28.1.tar.bz2 _eclasses_=eutils 32548a82e42dc26e3312581476d2f20c fdo-mime 0acfe1a88fd8751a1d5dc671168219fa gnome-python-common-r1 3ebf8436a00591c0d63aff2be3302433 gnome.org 8fef8f967214f56e08fa92d61163d891 gnome2 9637c29fc715b17a6328f24251129557 gnome2-utils f658eba3cc594a21cf6eef4af47daa90 libtool 52d0e17251d04645ffaa61bfdd858944 multibuild 46527a4656956da3d58acff72c9b59b1 multilib 3bf24e6abb9b76d9f6c20600f0b716bf multiprocessing d7f2985a2c76c365ee20269db5261414 python-r1 75e5c82b55dcb208a0a8f4ab8847e731 python-utils-r1 47dda904cf91c61f45b564d9f834fde1 toolchain-funcs 0f1760274637a138b99bb649202ea402 versionator cd0bcdb170807e4a1984115e9d53a26f _md5_=f1e6accf5b94f1fec367f77a4f7f8095 As to why that is ....
Looks like the REQUIRED_USE set in the eclass is simply lost in transit. I removed the line out of my local ebuild, and forced a cache regen, and low and behold, the REQUIRED_USE statement vanished from the cache. Added it back in, regen cache, it comes back. ( Also, in the absence of the cache, adding/removing REQUIRED_USE from the ebuild itself still changes the behaviour ). Which leads me to belive portage simply doesn't let you change that variable in an eclass.
Alternatively ... this typo may be a problem ;) REQUIRED_USE=${PYTHON_REQUIRED_SUE} If you want to be sued, you need only ask a helpful lawyer :) Fixing this line in the eclass to read "USE" instead of "SUE" also appears to fix this problem :)
+ 27 Sep 2014; Pacho Ramos <pacho@gentoo.org> gnome-python-common-r1.eclass: + Fix typo (#523856 by Kent Fredric) + hehe, how easy is to miss typos :D Thanks a lot for finding it ;)
