| Summary: | x11-proto/xcb-proto installs python files in /xcbgen/ | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ta2002 <throw_away_2002> |
| Component: | Eclasses | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | mattst88, python |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
x11-proto:xcb-proto-1.8-r1:20130621-113026.log
/var/db/pkg/x11-proto/xcb-proto-1.8-r1/environment.bz2 |
||
|
Description
ta2002
2013-06-21 18:35:51 UTC
Please attach environment too. Created attachment 351612 [details]
/var/db/pkg/x11-proto/xcb-proto-1.8-r1/environment.bz2
Hope this is what you meant. :)
testuser@archtester ~/cvsPortage/gentoo-x86/x11-proto/xcb-proto $ qlist xcb-proto |grep gen /usr/lib64/python3.2/site-packages/xcbgen/xtypes.py /usr/lib64/python3.2/site-packages/xcbgen/matcher.pyc plus another 20 or so lines of entry damned if I can figure how you did that... xcb-proto-1.8-r?.ebuild also comes in options xcb-proto-1.8-r[2-3].ebuild. I suggest you try those 2 and see if this oddity extends to those too. I think I figured out what happened.
Take a look at these lines in the log file:
checking for /usr/bin/python2.7 version...
checking for /usr/bin/python2.7 platform...
checking for /usr/bin/python2.7 script directory...
checking for /usr/bin/python2.7 extension module directory...
On another machine with a proper installation, those lines are:
checking for /usr/bin/python2.7 version... 2.7
checking for /usr/bin/python2.7 platform... linux2
checking for /usr/bin/python2.7 script directory... ${prefix}/lib64/python2.7/site-packages
checking for /usr/bin/python2.7 extension module directory... ${exec_prefix}/lib64/python2.7/site-packages
I don't think those checks should allow empty values there (they should fail), but that explains installing those files off of the root directory.
As for the reason for the empty values, a qcheck of dev-lang/python-2.7.3-r3 revealed a damaged /usr/bin/python2.7 (which a reinstall of python repaired). After fixing python, xcb-proto installed correctly.
I wonder if the issue is xcb-proto-specific, or generic issue with the macros. @x11: do we want to proxy this upstream or just do not care? I'm planning to look into this. Sorry for not getting to it sooner. Please reopen if this is still a problem. Thanks. |
