Many thanks, Toby. Reading between the lines of the howto you referred to, I think, if I am not mistaken, that the problem was that the monolithic-to-individual-package migration path built into 3.4.0 was removed from 3.4.1. Somehow this left the kde-3.4.0 ebuild hanging around as a kind of ghost even though all the individual kde packages updated to 3.4.1.
Running "emerge -C kde" didn't remove any actual kde packages, but it did clear the blockage and has allowed "emerge -u world" to proceed as it should. On July 9, 2005 04:53 pm Toby Cubitt was like: > On Sat, Jul 09, 2005 at 02:41:11PM -0700, Robert Persson wrote: > > A couple of weeks ago I added all the kde-3.4.1 packages to > > package.keywords and then ran emerge -u world and everything updated and > > ran fine. > > > > Today I tried to emerge -u world and I got > > > > [blocks B ] =kde-base/kdeartwork-icewm-themes-3.4* (is blocking > > kde-base/kdeartwork-3.4.1) > > ... blah blah blah ... > > [blocks B ] =kde-base/renamedlg-images-3.4* (is blocking > > kde-base/kdeaddons-3.4.1) > > > > for about 150 kde packages altogether. > > > > equery tells me that I have version 3.4.1 of each individual kde package > > installed, but that I have version 3.4.0 of kde itself and that I don't > > have kdeartwork, kdeaddons, kdebase etc. installed. > > > > How did I get in this mess and how (without recompiling all of kde) do I > > get out of it? > > I had a similar problem with upgrading when 3.4 was unmasked. The problem > is moving from the old monolithic ebuilds to the new split ones. I believe > it's because you are trying to install both split and unsplit ebuilds that > provide some of the same programs. > > My solution to sort out the mess was to unmerge all the monolithic kde > ebuilds, and then emerge the stuff I wanted (kdebase-startkde is the split > ebuild that provides the basic stuff like the window manager, though even > that isn't necessary if you only want to run some kde apps and not the full > kaboodle). > > It sounds like you might already have the new split ebuilds installed, so > you might just need to remove the monolithic ones from your world file, or > possibly unmerge them if they're still around. Of course, that assumes you > want to use the split ebuilds. > > If you haven't read it already, the How-To at > > http://gentoo-wiki.com/HOWTO_Update_KDE_3.3_to_KDE_3.4 > > is helpful. A bit of research with the online package database to work out > which ebuilds are the split ones, which the monolithic ones, and which ones > you actually want should sort you out. -- Robert Persson "Don't use nuclear weapons to troubleshoot faults." (US Air Force Instruction 91-111, 1 Oct 1997) -- gentoo-user@gentoo.org mailing list
