Version 3.3.1 of most of KDE has just been unmasked, but kdegraphics is still at 3.3.0-r2. So when I updated a machine, it compiled kdelibs-3.3.1 and later kdegraphics-3.3.0, which failed (probably due to the wrong version of kdelibs, but the error message had scrolled off the screen). I then wanted to try again, but this time it wanted to downgrade kdelibs to 3.3.0, probably because kdegraphics wants that version. I assume that either kdegraphics 3.3.1 should have been unmasked, or the rest of KDE should have remained masked. I will refrain from updating this machine until the portage tree has become consistent again - in particular since it takes a while to compile KDE :-) Reproducible: Always Steps to Reproduce: 1. 2. 3. demokrit root # esearch kdelibs kdebase kdegraphics [ Results for search key : kdelibs ] [ Applications found : 2 ] * app-doc/kdelibs-apidocs Latest version available: 3.1.5 Latest version installed: [ Not Installed ] Size of downloaded files: [no/bad digest] Homepage: http//developer.kde.org/ Description: API documentation autogenerated from the kde-base/kdelibs package * kde-base/kdelibs Latest version available: 3.3.1 Latest version installed: 3.3.0 Size of downloaded files: [no/bad digest] Homepage: http//www.kde.org/ Description: KDE libraries needed by all kde programs [ Results for search key : kdebase ] [ Applications found : 1 ] * kde-base/kdebase Latest version available: 3.3.1 Latest version installed: 3.3.0 Size of downloaded files: [no/bad digest] Homepage: http://www.kde.org/ Description: KDE base packages: the desktop, panel, window manager, konqueror... [ Results for search key : kdegraphics ] [ Applications found : 1 ] * kde-base/kdegraphics Latest version available: 3.3.0-r2 Latest version installed: 3.3.0-r1 Size of downloaded files: [no/bad digest] Homepage: http://www.kde.org/ Description: KDE graphics-related apps demokrit root # emerge info Portage 2.0.51-r2 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9 i686) ================================================================= System uname: 2.6.9 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /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=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/var/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ ftp://trumpetti.atm.tut.fi/gentoo/ ftp://ftp.rhnet.is/pub/gentoo/ ftp://gd.tuwien.ac.at/opsys/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/var/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X Xaw3d acpi alsa arts atlas avi berkdb bitmap-fonts cdr crypt cups dga dvd emacs encode fam foomaticdb gdbm gif gpm gtk gtk2 imap imlib java jpeg kde libg++ libwww mad maildir mbox mikmod motif mozilla mpeg mule ncurses netcdf nls nptl oggvobis oggvorbis opengl oss pam pcmcia pdflib perl png pnp ppds python qt quicktime readline scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype trusted usb wxwindows x86 xml2 xmms xv xvid zlib" demokrit root #
i have exactly the same problem :S
i can confirm this one
confirmed
see Bug 69998. There is a comment in there that this was done on purpose because they wanted to see how stable the unmasked 3.3.1 pieces were before unmasking everything. I find this appalling and unacceptable (them's fighting words, eh) :). Unmasked, stable packages should not be "testing" grounds for someone to "wanted to validate the stability of kdelibs and kdebase before I put the rest stable." Unmasked stable packages are supposed to already have been validated for stability. The biggest problem with the unmasking is that a vast majority of people use the kde catch all package to install KDE. This has dependencies for 3.3.0 (since that's still the latest stable version of the catch-all package). Until 3.3.1 is entirely stable, every emerge update will either attempt to upgrade the unmasked packages to 3.3.1 and then downgrade them to 3.3.0 the next time. This is rather silly and results in wasting ALOT of cpu power for a "testing" process that should have been accomplished prior to unmasking. Of course, I'm standing on a soapbox now :).
Calm down - the "testing" I was referring to was some local testing I wanted to do to ensure that some of the issues I had with kdepim, kdegraphics, and others were not passed on to all of the other users. I unmasked kdelibs and kdebase so we could start the process of clearing up the security issue with kdegraphics on all of the architectures.
Created attachment 43354 [details] 2.6.9 .config for the Dell Inspiron also showing the problem.
Comment on attachment 43354 [details] 2.6.9 .config for the Dell Inspiron also showing the problem. Oops! I wanted to attach this to another bug, that I had just been commenting on. But bugzilla had moved unto the next bug on My Bugs. Sorry!!
Caleb, My comment was somewhat tongue in cheek :), and I can see why it was done, but it's just not a good thing when it results in goofy upgrade/downgrading loops.
I understand. Should be fixed now in portage anyway.
*** Bug 70204 has been marked as a duplicate of this bug. ***
*** Bug 70139 has been marked as a duplicate of this bug. ***
*** Bug 70316 has been marked as a duplicate of this bug. ***
It looks like it was fixed over the weekend - the new KDE is up and running. Thanks folks! I guess it means this bug is resolved. Is it OK for me as the one reporting the bug to mark it FIXED, or is that best left for the developpers. I guess the latter... :-) /Jakob
Thank for testing. If it works for you that are the reporter then I'll close the bug.
