Created attachment 358644 [details] emerge --info output from elogv: INFO: setup │ │Package: app-emulation/spice-0.12.3-r1 │ │Repository: gentoo │ │Maintainer: dev-zero@gentoo.org virtualization@gentoo.org │ │USE: amd64 elibc_glibc kernel_linux userland_GNU │ │FEATURES: installsources preserve-libs sandbox splitdebug userpriv │ │usersandbox │ │ERROR: setup │ │No Python implementation found for the build. This is usually │ │a bug in the ebuild. Please report it to bugs.gentoo.org │ │along with the build log. │ │ERROR: app-emulation/spice-0.12.3-r1::gentoo failed (setup phase): │ │ No supported Python implementation installed. │ │ │ │Call stack: │ │ ebuild.sh, line 93: Called pkg_setup │ │ spice-0.12.3-r1.ebuild, line 64: Called python-any-r1_pkg_setup │ │ python-any-r1.eclass, line 252: Called die │ │The specific snippet of code: │ │ die "No supported Python implementation installed." │ Following the python trail, I found that the command: emerge -uavDN @world didn't found anything, but the command: emerge -upv pyparsing did find the update to 2.0.1. After updating pyparsing, the spice update went like a charm. Solved for me, but looks strange to me ...
The python herd explained that this is something to due with their stabilization process. I'll punt it over to them for some more details.
The ${PYTHON_USEDEP} part of the has_version check fails if you have an older version of pyparsing installed. I modified it to depend on a version of pyparsing which exports the python_targets use flags. + 16 Sep 2013; Mike Gilbert <floppym@gentoo.org> spice-0.12.3-r1.ebuild, + spice-0.12.4.ebuild: + Require a python-r1 compatible version of dev-python/pyparsing, bug 484906.
By the way, I feel like python_check_deps() in any-r1 was a bad idea. We can't enforce any impl from PYTHON_COMPAT to happen in the dep. So unless we get something like: dev-python/foo[python_targets_X|python_targets_Y|python_targets_Z] in EAPI, python-single-r1 seems like a better solution.
