| Summary: | dev-python/apipkg fails tests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Build log | ||
|
Description
Diego Elio Pettenò (RETIRED)
2010-10-18 18:59:24 UTC
Created attachment 251159 [details]
Build log
gentoo64 enable # sr
gentoo64 enable # gt
FEATURES="userpriv usersandbox multilib-strict
gentoo64 enable # emerge apipkg
gentoo64 enable # sadd
gentoo64 enable # gt
FEATURES="userpriv test usersandbox multilib-strict
gentoo64 enable # emerge apipkg
>>> Emerging (1 of 1) dev-python/apipkg-1.0 from progress
>>> Installing (1 of 1) dev-python/apipkg-1.0
Well the mysteries of python tests. You need emerge apipkg first, then it seems to draw from the installed instance to run the tests. Offhand I don't yet know how to redirect the paths in the source, but this is the epitome of wt*.
Surely the tests should draw upon its own build to import apipkg.
+ 19 Jun 2012; Patrick Lauer <patrick@gentoo.org> +apipkg-1.2.ebuild: + Bump, fixes #341673 #421793 |