| Summary: | sys-apps/pkgcore-0.5.5 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robin Johnson <robbat2> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | ferringb |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Robin Johnson
2009-12-09 22:35:09 UTC
play w/ the python version, doing an import of snakeoil- (python${VER} -c 'import snakeoil' specifically).
Pkgcore now relies on snakeoil during it's build/install phase. My bet, portage is invoking pkgcore's setup.py w/ 3.1, and no snakeoil is available for 3.1...
for i in 2.5 2.6 3 3.1 ; do echo === $i ; python${i} -c 'import snakeoil' ; done ;
=== 2.5
=== 2.6
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named snakeoil
=== 3
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named snakeoil
=== 3.1
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named snakeoil
Default python IS set to 2.6 here. So it's NOT a py3k issue.
Doing: "emerge snakeoil pkgcore" fixed the issue. So the question is what was wrong with the previous copy of snakeoil? It was probably bug #295340. Snakeoil ebuild was relying (and partially still relies) on internals of some eclasses. *** This bug has been marked as a duplicate of bug 295340 *** |