Created attachment 362684 [details] emerge --info This is similar to bug #472054 and bug #466408 Maybe its a bug for the eclass? Not sure. Either way, PYTHON_SINGLE_TARGET requires at least one value specified in its own list of values. So if you have, for instance PYTHON_SINGLE_TARGET=python3_3, xen-tools fails because it expects either python2_7 or python2_6, and it fails during pkg_setup, where it should fail at USE resolution. >>> Emerging (2 of 2) app-emulation/xen-tools-4.2.2-r3 * xen-4.2.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * ipxe.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * seabios-0-20121121.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * XSA-55patches.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * No Python implementation selected for the build. Please set * the PYTHON_SINGLE_TARGET variable in your make.conf to one * of the following values: * * python2_6 python2_7 * ERROR: app-emulation/xen-tools-4.2.2-r3::gentoo failed (setup phase): * No supported Python implementation in PYTHON_SINGLE_TARGET. * * Call stack: * ebuild.sh, line 93: Called pkg_setup * xen-tools-4.2.2-r3.ebuild, line 86: Called python-single-r1_pkg_setup * python-single-r1.eclass, line 259: Called python_setup * python-single-r1.eclass, line 249: Called die * The specific snippet of code: * die "No supported Python implementation in PYTHON_SINGLE_TARGET." * * If you need support, post the output of `emerge --info '=app-emulation/xen-tools-4.2.2-r3::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/xen-tools-4.2.2-r3::gentoo'`. * The complete build log is located at '/var/log/portage/build/app-emulation/xen-tools-4.2.2-r3:20131106-161641.log.gz'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emulation/xen-tools-4.2.2-r3/temp/build.log.gz'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/xen-tools-4.2.2-r3/temp/die.env'. * Working directory: '/usr/lib64/portage/pym' * S: '/var/tmp/portage/app-emulation/xen-tools-4.2.2-r3/work/xen-4.2.2'
Maybe its a bug for the eclass? Hmm well it could be and I'm not really sure, but I'd say mgorny would say no. Consider 16 Dec 2012; Michał Górny <mgorny@gentoo.org> +xen-tools-4.2.0-r2.ebuild: Migrate to python-r1, clean up a bit. Acked by idella4. meaning he did the conversion on asking him back then. Let's just CC him and he can peruse and choose.
Given the bugs similarity to bug #490578 it may just be a case of using the eclass wrongly. I just realised I didn't report the version of xen-tools , my bad: 4.2.2-r3 Though it might be a problem with other versions.
+ 09 Nov 2013; Michał Górny <mgorny@gentoo.org> xen-tools-4.2.2-r3.ebuild, + xen-tools-4.2.2-r5.ebuild, xen-tools-4.3.0-r3.ebuild: + Add missing PYTHON_REQUIRED_USE.
