| 1 |
Hello, |
| 2 |
|
| 3 |
After a sync, portage wants to upgrade pykde from the currently installed |
| 4 |
3.16.0-r1 (which is now masked) to 3.16.2, but source configuration fails |
| 5 |
with an error: |
| 6 |
|
| 7 |
[...] |
| 8 |
Creating top level Makefile... |
| 9 |
Creating pykdeconfig.py... |
| 10 |
[...] |
| 11 |
sipkdecoreNETRootInfo3.cpp: In constructor ‘sipNETRootInfo3::sipNETRootInfo3 |
| 12 |
(void*, long unsigned int, const char*, long unsigned int*, int, int, |
| 13 |
bool)’: |
| 14 |
sipkdecoreNETRootInfo3.cpp:104: error: invalid conversion from ‘void*’ |
| 15 |
to ‘Display*’ |
| 16 |
sipkdecoreNETRootInfo3.cpp:104: error: initializing argument 1 |
| 17 |
of ‘NETRootInfo3::NETRootInfo3(Display*, Window, const char*, long unsigned |
| 18 |
int*, int, int, bool)’ |
| 19 |
make[1]: *** [sipkdecoreNETRootInfo3.o] Error 1 |
| 20 |
|
| 21 |
Looking at b.g.o I see that PyQt is sometimes implicated in pykde |
| 22 |
difficulties, so I tried that tack. This is what I found: |
| 23 |
|
| 24 |
prh@wstn ~ $ equery l PyQT |
| 25 |
[ Searching for package 'PyQT' in all categories among: ] |
| 26 |
* installed packages |
| 27 |
prh@wstn ~ $eix pyqt |
| 28 |
[I] dev-python/PyQt (3.17.4@14/11/08): A set of Python bindings for Qt3 |
| 29 |
[N] dev-python/PyQt4 (4.3.3): PyQt is a set of Python bindings for the Qt |
| 30 |
toolkit |
| 31 |
Found 2 matches. |
| 32 |
prh@wstn ~ $ emerge -pv PyQT |
| 33 |
[...] |
| 34 |
emerge: there are no ebuilds to satisfy "PyQT". |
| 35 |
|
| 36 |
Summary: eix thinks I have dev-python/PyQT-3.17.4 installed, but equery and |
| 37 |
portage think there's no such package as PyQT. This has been happening for |
| 38 |
a few days now, with a daily emerge --sync and update-eix. |
| 39 |
|
| 40 |
Do I have a corrupted package database? How can I get out of this? |
| 41 |
|
| 42 |
-- |
| 43 |
Rgds |
| 44 |
Peter |
Archives