previous summary upgrade from kde 3.2.0 to 3.2.1 resulted in UD kde3.2.0 being reinstalled durring it background This could be my "misuse" of the tools... but it's what i've had to do to keep up to date... I have an alsa-tools 1.03 package that just won't install, so I have to emerge everything that shows up after it with emerge x; emerge y ; emerge z; etc what my misuse might be: Now.. I like doing -uD as the emerge options.. this could be my big problem here... Time: This was right before the kde 3.2.1 was officially released Results: My computer apperantly compiled and recompiled kde 3.2.0 and kde 3.2.1 Possible work arround... I'm going to switch my flags to -UD but what problems are associated with that? Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Perhaps there was an ebuild that had a hard dpendancy on kde 3.2.0 , perhaps that should have be a dependancy on kde 3.2.1 or perhaps... The virtual ebuild was the last thing to get into portage, and when I ran emerge kde -uD after that, it did something wierd.. The whole point of this is not my story... it's that portage changes, and occasionaly gets into a state where these conditions are more likely to happen. What can we do about them?
Sounds like a misuse of the tools. -uD won't necessarily install the latest version, especially if the latest version is "~unstable". If you install it manually, then you either need to set up portage to ignore it in the /etc/portage directory, or change your keywords, or use -UD.
I also have this problem right now with gtk+ it keeps on swapping between 2.4 and 2.2 even without the -D! bash-2.05b# emerge --info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.4-gentoo-r1) ================================================================= System uname: 2.6.4-gentoo-r1 i686 AMD Athlon(TM) XP 1700+ Gentoo Base System version 1.4.3.13p1 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/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="-march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X aalib acpi acpi4linux alsa amd apache2 apm arts artswrappersuid avi berkdb bonobo cdr cjk cjkcrypt crypt cscope cups dga directfb doc dv dvb dvd encode esd evms2 faad fbcon ffmpeg flac flash foomaticdb freetype fs gdbm ggi gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imap imlib jack java javascript joystick jpeg kde kerberos krb4 ldap libcss libdvdread libg++ libwww mad maildir md5sum mdb mikmod mmx motif mozilla mpeg mpeg4 mule mysql nas ncurses net nls nptl nvidia oggvorbis opengl oss pam pdflib perl pic png python qt quicktime readline samba sasl scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff transcode truetype unicode usb v4l vhosts virus-scan x86 xine xinerama xml2 xmms xv xvid zeo zlib"
Bah... this is basically a dupe of an older portage bug I'm unable to find...
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Closing due to old age