When I want to run a python programm, I get the following error message: Traceback (most recent call last): File "/usr/bin/autokey", line 5, in <module> from autokey.autokey import Application File "/usr/lib/python2.6/site-packages/autokey/autokey.py", line 25, in <module> import service, ui.notifier, ui.popupmenu, ui.configwindow, ui.abbrselector File "/usr/lib/python2.6/site-packages/autokey/service.py", line 21, in <module> from iomediator import Key, IoMediator File "/usr/lib/python2.6/site-packages/autokey/iomediator.py", line 90, in <module> from interface import * File "/usr/lib/python2.6/site-packages/autokey/interface.py", line 30, in <module> from Xlib.ext import record, xtest ImportError: cannot import name record For me It seems that python-xlib is missing the Xlib.ext module. Reproducible: Always Steps to Reproduce: 1. Install autokey 2. Run Autokey 3. Actual Results: programm won't run Expected Results: Programm will run smoothly
I think what you need is the testing-graded version of dev-python/python-xlib (0.14). The current stable python-xlib is 0.12-r3, has base source from year 2002 (I think). SourceForge SVN Browse shows that Xlib.ext.record was only added in 2006, so you will need the newer version.
(In reply to comment #1) > I think what you need is the testing-graded version of dev-python/python-xlib > (0.14). > > The current stable python-xlib is 0.12-r3, has base source from year 2002 (I > think). SourceForge SVN Browse shows that Xlib.ext.record was only added in > 2006, so you will need the newer version. > Oke, But version 0.14 is not stable. So persons which want to use my ebuild are forced to make a mix between stable and unstable now. I hope that .014 will be stable soon. Roelof
(In reply to comment #2) > But version 0.14 is not stable. > So persons which want to use my ebuild are forced to make a mix between stable > and unstable now. > I hope that .014 will be stable soon. Ok, there is an ebuild? Before doing anything else, update the ebuild to depend on something like ">=dev-python/python-xlib-0.14", just to ensure a recent enough python-xlib. As for the stabilization, it needs a stabilization request bug. I'm not sure if the devs will accept it if you just change the title of this bug into something like "Stabilization request for dev-python/python-xlib-0.14". Maybe it's worth a try? Otherwise you'll need to file a separate bug.
Please stabilize dev-python/python-xlib-0.14.
amd64 done
HPPA doesn't have python-xlib keyworded. If you intended to state a keyword request, please do so explicitly (and re-CC us).
(In reply to comment #6) > HPPA doesn't have python-xlib keyworded. If you intended to state a keyword > request, please do so explicitly (and re-CC us). I probably accidentally pressed HPPA entry instead of IA64 in the list of architectures.
(In reply to comment #7) > (In reply to comment #6) > > HPPA doesn't have python-xlib keyworded. If you intended to state a keyword > > request, please do so explicitly (and re-CC us). > > I probably accidentally pressed HPPA entry instead of IA64 in the list of > architectures. > Oke, And how about the x86 architectures ? Roelof
(In reply to comment #8) > And how about the x86 architectures ? x86@gentoo.org is already in the CC list. (dev-python/python-xlib-0.12-r3 is stable on x86.)
Stable on alpha.
ppc stable
All done