Hopefully self explanetary. Does not try to downgrade without the -D (deep) option. It still downgrades when the -U (upgrade-only) option is used (-uUD). I had a similar problem with the nvidia dirvers while running the 4191 (~x86) drivers on a mostly 'x86' box. This may be a dup of that problem... I now have a fully '~x86' box. I don't know if the problem lies with portage's logic or the ebuilds' specified dependancies, so am entering this separate bug entry. This is the contents of my world file: app-text/docbook-sgml-dtd net-p2p/dc-gui sys-apps/reiserfsprogs net-print/foomatic dev-util/dmake media-sound/alsa-utils app-text/acroread app-arch/rar sys-kernel/linux-headers media-video/dvdrip media-sound/lame media-sound/bladeenc sys-apps/vcron net-analyzer/traceroute x11-plugins/gkrellm-volume media-libs/fontconfig media-sound/grip net-ftp/easyftp media-libs/xine-lib app-office/abiword media-sound/cdparanoia app-cdr/arson media-gfx/sane-frontends net-www/phoenix-bin app-cdr/cdbakeoven net-www/lynx media-sound/alsa-driver media-libs/libvorbis app-cdr/k3b media-video/nvidia-kernel app-cdr/cdrtools sys-kernel/gentoo-sources app-cdr/cdrdao media-video/xine-ui app-crypt/gnupg app-admin/gkrellm kde-base/kde x11-plugins/gkrellmms media-video/nvidia-glx media-sound/normalize app-admin/metalog net-ftp/kbear x11-base/xfree beekster01 root # emerge -puv world These are the packages that I would merge, in order: Calculating world dependencies ...done! beekster01 root # emerge -puDv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] kde-base/kdelibs-3.1-r2 [3.1-r3] +alsa +cups +ipv6 +ssl beekster01 root # emerge -puUDv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] kde-base/kdelibs-3.1-r2 [3.1-r3] +alsa +cups +ipv6 +ssl I wouldn't mind so much if it weren't such a long build! :) If you need any other info from my system, please let me know. Gentoo Rocks. Reproducible: Always Steps to Reproduce: 1. emerge -puD world 2. emerge -puD world 3. beekster01 root # emerge info Portage 2.0.47-r8 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r0) ================================================================= System uname: 2.4.19-gentoo-r10 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz GENTOO_MIRRORS="ftp://mirror.aarnet.edu.au/pub/gentoo http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/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="" USE="gtkhtml bonobo guile perl esd -3dnow acpi alsa apm arts avi berkdb crypt cups cdr dvd encode gdbm gif gnome gpm gtk gtk2 ipv6 imlib java jpeg kde libg++ libwww mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pdflib png python qt quicktime readline scanner sse sdl slang spell ssl svga tcpd truetype usb X x86 xml2 xmms xv zlib" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O3 -pipe -mmmx -msse -msse2 -fomit-frame-pointer" CXXFLAGS="-march=pentium4 -O3 -pipe -mmmx -msse -msse2 -fomit-frame-pointer" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
This bug is caused because kdebase-3.1-r1 has a dependancy that was not updated to point to kdelibs-3.1-r3. the line -------------------------------- newdepend "=kde-base/kdelibs-3.1-r2" -------------------------------- should be changed to -------------------------------- newdepend "=kde-base/kdelibs-3.1-r3" -------------------------------- Can someone with cvs access change this? Thanks Naren Sankar
I'm sorry about this situation. If only we had portage support for dep range specification, this wouldn't happen... I'm upgrading the kdebase dep to >=kdelibs-3.1-r2. That means kdelibs-5 (the cvs ebuild) will satisfy it too but better that than this problem for all the ~x86 profile ppl.
This situation will be remedied when we (very soon) go to kde 3.1.1 and start from r0 again, but it could be created again...
Now that we have 3.1.1, 3.1.1a and (soon) 3.1.2, this bug should not longer be valid.
