sys-libs/tdb-1.2.1-r1 neglects to honor the eselected python version and keeps installing into 2.6 site-packages instead of eselected python 2.7 destination. Reproducible: Always Steps to Reproduce: 1. Just emerge tdb with eselected python 2.7.x Actual Results: Python bindings are buitl for 2.6 Expected Results: Python bindings for eselected version Seems to be a problem in the configure script which explicitly only looks for python up to version 2.6.
Choose. Either a dupe of bug 297576 or a dupe of bug 316959.
BUG 297576 results in a build error, this does not seem to be related, since building tdb works (just the python object is put in the wrok site-packages dir). BUG 316959 is somewhat related, but it's not just an QA issue, since the result is more drastic. We could say it is a dupe of 316959 if that errors priority is increased accordingly.
Not, really, you need to read the bug more carefully (and your own build log probably too). While the build failure itself is python3 related, the python module is not simply placed in python 2.6 dir, the module is *built* against python 2.6.
You are right, I did not express this properly, it is built against 2.6 (that's why I pointed at the configure script) and placed in the corrsponding dir. Still, it is only loosely related to the QA bug.
*** This bug has been marked as a duplicate of bug 316959 ***
