pykde-3.7.4 successfully builds then silently fails to install with the following errors: make[1]: Leaving directory `/var/tmp/portage/pykde-3.7.4/work/PyKDE-3.7-4/kdeprint' >>> Install pykde-3.7.4 into /var/tmp/portage/pykde-3.7.4/image/ category dev-python ( [ -d dcop ] & "/usr/bin/make" -f Makefile install; ) || true make[1]: Entering directory `/var/tmp/portage/pykde-3.7.4/work/PyKDE-3.7-4/dcop' cp dcop.py /var/tmp/portage/pykde-3.7.4/image//usr/lib/python2.2/site-packages cp: cannot create regular file `/var/tmp/portage/pykde-3.7.4/image//usr/lib/python2.2/site-packages': No such file or directory make[1]: [install] Error 1 (ignored) cp dcop.pyc /var/tmp/portage/pykde-3.7.4/image//usr/lib/python2.2/site-packages cp: cannot create regular file `/var/tmp/portage/pykde-3.7.4/image//usr/lib/python2.2/site-packages': No such file or directory and so on for all the packages. Despite this, portage claims successful installation. >>> dev-python/pykde-3.7.4 merged. dev-python/pykde selected: none protected: 3.7.4 omitted: none Reproducible: Always Steps to Reproduce: 1. emerge pykde 2. 3. Expected Results: Copies the pykde packages to /usr/lib/python-2.2/site-packages
--> #27401
Fair enough, bug #27401 is the same as this. However I did search for pykde in open bugs before submitting this one: #27401 is marked as fixed, although the ebuild script isn't actually fixed. I guess someone with cvs access needs to do it, so presumably it's worth keeping this bug open to track it till it's done? cheers Julian
I too am having issues with PyKDE not being installed correctly. It would be nice if someone could fix this bug sometime soon...
ok .. i'm committing the changes to pykde, can you guys test it for me because i don't have KDE installed
Great stuff, works for me now! thanks Alastair.. cheers, Julian
thanks. closing this then
