Bug 25234 – Bad handling of blocking dependecies with kde

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Alastair Burt 2003-07-25 00:38:29 UTC]

I have KDE 3.1.2 installed and it works fine. I updated portage to 2.0.48-r5 and
now I am told that I cannot 'emerge -uD world' because:

[blocks B    ] =kde-base/kdebase-3.1.1 (from pkg x11-libs/qt-3.1.2-r3)

As far as I can see, there is no need to install kdebase-3.1.1 so emerge should
not block.

Reproducible: Always
Steps to Reproduce:
1. emerge -uD world

I think anything that depends on kde will cause this, as for example:

   emerge -uD arts

Actual Results:  
I see:

  [blocks B    ] =kde-base/kdebase-3.1.1 (from pkg x11-libs/qt-3.1.2-r3)

Expected Results:  
It should not report a blocking dependency.

root:~ $ emerge info
Portage 2.0.48-r5 (default-1.0, gcc-2.95.3, glibc-2.2.5-r8,2.2.5-r4)
=================================================================
System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) Processor
GENTOO_MIRRORS="ftp://gentoo.linux.no/pub/gentoo
ftp://ftp.tu-clausthal.de/pub/linux/gentoo
ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/portage"
USE="x86 oss 3dnow apm libg++ mikmod ncurses quicktime xml2 aalib berkdb bonobo
directfb esd gdbm ggi gnome gpm gtkhtml guile imlib java ldap libwww motif nls
oggvorbis pam perl slang svga tcpd tiff alsa arts avi cdr crypt cups encode gif
gphoto2 gtk jpeg kde mmx mozilla mpeg oggvobis opengl pdflib png python qt
readline scanner sdl spell ssl tcltk tetex truetype usb wmf X xmms xv dvd fbcon
flash gd imap lcms mule pda xface xml zeo zlib -gnome-libs -nas"
COMPILER=""
CHOST="i686-pc-linux-gnu"
CFLAGS="-O3 -march=i686 -pipe -O3 "
CXXFLAGS="-O3 -march=i686 -pipe -O3 "
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage/"
FEATURES="sandbox ccache digest fixpackages"

root:~ $ etcat -v kdebase
[ Results for search key : kdebase ]
[ Applications found : 1 ]

*  kde-base/kdebase :
        [   ] kde-base/kdebase-2.2.2-r5 (2.2)
        [   ] kde-base/kdebase-3.0.4-r3 (3.0)
        [   ] kde-base/kdebase-3.0.5b (3.0)
        [   ] kde-base/kdebase-3.1.1a (3.1)
        [  I] kde-base/kdebase-3.1.2 (3.1)
        [M~ ] kde-base/kdebase-3.1.3 (3.1)

[Comment 1 Paul de Vrieze (RETIRED) 2003-07-25 01:45:04 UTC]

What version of qt have you installed? Could you try first to manually update qt to the latest version, and try again.

[Comment 2 Alastair Burt 2003-07-25 02:32:09 UTC]

I already have the latest unmasked versions of qt and arts installed. They were installed with an older version of portage that did not complain about the blocking dependencies.

$ etcat -v qt

*  x11-libs/qt :
        [  I] x11-libs/qt-2.3.2-r1 (2)
        [   ] x11-libs/qt-3.0.5-r2 (3)
        [  I] x11-libs/qt-3.1.0-r3 (3)
        [M~ ] x11-libs/qt-3.1.1-r2 (3)
        [  I] x11-libs/qt-3.1.2-r3 (3)
        [M~ ] x11-libs/qt-3.1.2-r4 (3)
        [M~ ] x11-libs/qt-3.1.2-r5 (3)
        [M~ ] x11-libs/qt-3.2.0_beta1 (3)
        [M~ ] x11-libs/qt-3.2.0_beta2 (3)

$ etcat -v arts

*  kde-base/arts :
        [   ] kde-base/arts-1.0.4-r1 (3.0)
        [   ] kde-base/arts-1.0.5b (3.0)
        [   ] kde-base/arts-1.1.1 (3.1)
        [  I] kde-base/arts-1.1.2 (3.1)
        [M~ ] kde-base/arts-1.1.2-r1 (3.1)
        [M~ ] kde-base/arts-1.1.3 (3.1)

[Comment 3 Paul de Vrieze (RETIRED) 2003-07-25 02:43:04 UTC]

You have two conflicting qt versions installed. Please run
emerge -C =x11-libs/qt-3.1.0-r3, that should fix things hopefully

[Comment 4 Alastair Burt 2003-07-25 04:32:14 UTC]

I unmerged qt-3.1.0 as suggested, but I still had the blocking problem. Clutching at straws, I then did a sync, which showed that there was an update of portage. After installing portage 2.0.48-r6, I no longer get the blocking messages; I get something worse:

!!! aux_get(): ebuild for '=kde-base/kdebase-3.1.1' does not exist at:
!!!            /usr/portage/=kde-base/kdebase/kdebase-3.1.1.ebuild
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1978, in ?
    mydepgraph.display(mydepgraph.altlist())
  File "/usr/bin/emerge", line 943, in display
    if ("fetch" in string.split(portage.portdb.aux_get(x[2],["RESTRICT"])[0])):
  File "/usr/lib/python2.2/site-packages/portage.py", line 3435, in aux_get
    raise KeyError
KeyError

[Comment 5 Alastair Burt 2003-07-27 12:23:01 UTC]

Getting back to a usable version of portage, I did:

  emerge unmerge kdebase && emerge kdebase

After a couple of hours compilation, I had my sytem back in order and emerge world no longer blocks.

So despite the output of etcat that I cut and pasted into my first posting, emerge still considered that some version of kdebase-3.1.1 was installed on my system.

In short, there is no bug in portage or the ebuilds.

[Comment 6 Paul de Vrieze (RETIRED) 2003-07-28 04:49:38 UTC]

Ok, I'll resolve the bug