Bug 45859 – deep emerge (emerge -uD) keeps rolling KDE back and forth (3.2.1<->3.2.0)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Dave Andruczyk 2004-03-26 19:25:41 UTC]

I use emerge world -uD to keep my box up to date, and for the past two weeks (since about 2 days after KDE 3.2.1 came out) emerge world -uD keeps trying to roll back arts from 1.2.1, kdelibs, kdebase, and kdenetwork, from 3.2.1 to 3.2.0.  

If I let it, it'll rollback, then on the next emerge -uD it'll go back to 3.2.1, subsequent runs keeps going back and forth...

Reproducible: Always
Steps to Reproduce:
1.emerge world -uD
2.emerge rsync (next day)
3. emerge world -uD	

Actual Results:  
first time (assuming kde 3.2.1 isn't up to date)  it installs all kde 3.2.1 stuff	 
next time it rolls back arts, kdebase, kdelibs, kdenetwork to 3.2.0 
following runs go to 3.2.1 again,  each time I update it tries to swap to another release... 

Expected Results:  
it should stop wanting to keep swapping versions 

emerge info: 
 
emerge info  
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25) 
================================================================= 
System uname: 2.4.25 i686 AMD Athlon(tm) MP 
Gentoo Base System version 1.4.3.13 
Autoconf: sys-devel/autoconf-2.58-r1 
Automake: sys-devel/automake-1.7.7 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-mcpu=athlon-mp -O2 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
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/bind /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-mcpu=athlon-mp -O2 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs ccache sandbox" 
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ 
ftp://gentoo.noved.org/" 
MAKEOPTS=" -j4 " 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="X aalib acl alsa apm arts avi berkdb bonobo cdr crypt cups curl dga dvb dvd encode esd 
foomaticdb freetype gdbm ggi gif gnome gphoto2 gpm gtk gtk2 guile imlib jack java joystick jpeg 
kde libg++ libwww mad mikmod mmx motif mozilla mpeg mysql nas ncurses nls oggvorbis opengl oss 
pam pdflib perl png python qt quicktime readline ruby samba scanner sdl slang spell ssl svga tcltk 
tcpd tetex truetype usb videos wmf x86 xft xml2 xmms xv zlib"

[Comment 1 Caleb Tennis (RETIRED) 2004-04-05 11:25:30 UTC]

perhaps you have some package installed that explicitly is relying on 3.2.0?  You can use the /etc/portage directory to filter this kind of stuff out - read the man page on portage for more information.

[Comment 2 Dave Andruczyk 2004-04-08 18:10:04 UTC]

How can I find out if a package (ebuild) is explicitly needing kde-3.2.0 ?  

If a package explicitly needs 3.2.0 but not 3.2.1 I consider that a bug in the package due the kde major and minor version being the same (only the micro version changed).

[Comment 3 Caleb Tennis (RETIRED) 2004-04-09 05:49:44 UTC]

I'm not sure, to be honest - some emerge command line options perhaps.  That's all I can think of for something that would want to continuously try and revert your kde version....

[Comment 4 Caleb Tennis (RETIRED) 2004-04-26 18:34:57 UTC]

marking as closed, as you can circumvent this behavior via portage config files (man portage).