Summary: | dev-python/libcloud-0.16.0 bump / test failure with py3.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://issues.apache.org/jira/browse/LIBCLOUD-643 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Lauer
2014-11-18 03:52:20 UTC
also; https://issues.apache.org/jira/browse/LIBCLOUD-642 This opened a Pandora's box. The current and the prospective version bump carry the same bugs. Giving it a few days for upstream to make a fix. ~/cvsPortage/gentoo-x86/dev-python/libcloud $ PYTHON_TARGETS=python3_3 ebuild libcloud-0.16.0.ebuild clean test
----------------------------------------------------------------------
Ran 5031 tests in 22.974s
OK
>>> Completed testing dev-python/libcloud-0.16.0
This is with /usr/lib64/python3.3/site-packages/lxml renamed temporarily.
This demonstrates the fix in pycrypto is effective. The break by installed lxml remains
From Arfrever; Python[xml] is needed by libcloud, at least when lxml is not used. It appears to require PYTHON_REQ_USE="lxml,ssl(+)" in ebuilds however this when not used state is what is being addressed in the bug in https://issues.apache.org/jira/browse/LIBCLOUD-642. For now awaiting upstream to respond. nothing after 2 weeks now Chrstmas |