Seems the dependencies for imgSeek is broken. It used to work, but after upgrading world (including python libs), it broke. >> imgSeek Starting imgSeek, please wait ... --------- Traceback ------------------ Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/imgSeekLib/ImgDB.py", line 46, in ? from qt import * File "/usr/lib/python2.3/site-packages/qt.py", line 24, in ? import libsip ImportError: No module named libsip Cause: You system doesn't seem to have PyQT installed. Please install it before running this application. See http://www.riverbankcomputing.co.uk/pyqt/download.php and http://imgseek.sourceforge.net/requirements.html -------------------------------------- You have found a bug, please help us by submitting the text above and a precise description of how you caused it to "http://imgseek.sourceforge.net/bugs" Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/imgSeekLib/imgSeekApp.py", line 31, in ? from imgSeekLib import Error, ImgDB, dbCallbacks, customWidgets File "/usr/lib/python2.3/site-packages/imgSeekLib/customWidgets.py", line 41, in ? class Q2SizePolicy(QSizePolicy): NameError: name 'QSizePolicy' is not defined imgSeek: Unable to find one of the modules required. Make sure imgSeek was installed properly. >> emerge search pyQT[ Results for search key : pyQT ] [ Applications found : 1 ] * dev-python/PyQt Latest version available: 3.12 Latest version installed: 3.12 Size of downloaded files: 742 kB Homepage: http://www.riverbankcomputing.co.uk/pyqt/ Description: set of Python bindings for the QT 3.x Toolkit License: GPL-2 Reproducible: Always Steps to Reproduce: 1. run 'imgSeek' from command line Actual Results: See the 'details' section above. Portage 2.0.50-r10 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.3-gentoo-r1) ================================================================= System uname: 2.6.3-gentoo-r1 i686 Intel(R) Pentium(R) III Mobile CPU 1133MHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ftp.rhnet.is/pub/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi apm arts avi berkdb bonobo cdr crypt cups dvd encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml imlib jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib"
Ugh, this always happens to me when i upgrade python. it is possible to copy the contents of /usr/lib/python2.2/site-packages/ to the new site-packages/ but its really best to re-emerge pyqt (and all your other python add-ons) But first, make sure that 'which python' points to python2.3
Yep, for the record, I did: # emerge unmerge PyQT sip # emerge -uavD imgseek which took care of it, it seems. Thanks. I'm slightly surprised that a) I'm allowed to remove packages that other packages depend on, and that b) a library upgrade breaks installed applications. I really like Gentoo, but this is not good enough, IMHO. Is there a way to fix this?
>I really like Gentoo, but this is not good enough, IMHO. Is there a way to fix this? No. Portage doesn't provide reverse dependency checking yet. If you upgrade sip/PyQt to newer (incompatible) versions, you have to rebuild depending stuff.
I can't tell from the bug report, but did you run python-updater? (Until we get dependency checking into portage (it's coming, but not too quickly), users who update python need to run python-updater afterwards, as prompted by the message after emerging the new version of python.) If python-updater is failing, then we have yet another bug to fix.
