Summary: | app-emulation/spice-0.12.3-r1 - ERROR: app-emulation/spice-0.12.3-r1::gentoo failed (setup phase): No supported Python implementation installed. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Denis de La Fortelle <caracol> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | virtualization |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info output |
Description
Denis de La Fortelle
2013-09-14 14:12:51 UTC
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. |