Summary: | dev-python/pycairo-1.10.0-r2: fails test with python 3.2.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=407037 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
Toralf Förster
2012-03-05 21:52:16 UTC
Created attachment 304335 [details]
build log
archtester pycairo # USE_PYTHON="2.7 3.2" ebuild pycairo-1.10.0-r2.ebuild clean test platform linux2 -- Python 3.2.2 -- pytest-2.2.3 collected 7 items test/api_test.py ...... test/examples_test.py . =========================== 7 passed in 0.88 seconds =========================== /usr/bin/py.test: '/usr/bin/py.test-3.2' does not exist indicates you have not got dev-python/pytest emerged. archtester pycairo # qfile py.test dev-python/pytest (/usr/bin/py.test) archtester pycairo # qfile py.test-3.2 dev-python/pytest (/usr/bin/py.test-3.2) From the ebuild test? ( dev-python/pytest )" So how you managed to miss getting pytest emerged attempting to run test phase for the package, there is in fact a way to do it. But I bet you didn't do it. So for the record, just how did you run test dev-python/pycairo-1.10.0-r2 ?? That has become the essence of the bug (The attached logfile is double-compressed: running gunzip on it twice gets me readable text). The relevant lines are these: * Testing of dev-python/pycairo-1.10.0-r2 with CPython 3.2... PYTHONPATH=/var/tmp/portage/dev-python/pycairo-1.10.0-r2/temp/tests/3.2/usr/lib/python3.2/site-packages py.test /usr/bin/py.test: '/usr/bin/py.test-3.2' does not exist which most likely means python-updater ended up rebuilding pycairo before pytest, which will not work. Please file a fresh bug if pycairo still fails with pytest (for python 3.2) present. We cannot currently fix this correctly: the eclasses currently in use do not let us express dependencies on "package X built for the same pythons as we are". python-updater/portage will sometimes order rebuilds incorrectly, causing failures like this one. The right fix for this will involve moving to a smarter eclass, which is a way off still. |