| 1 |
Many thanks, Toby. |
| 2 |
|
| 3 |
Reading between the lines of the howto you referred to, I think, if I am not |
| 4 |
mistaken, that the problem was that the monolithic-to-individual-package |
| 5 |
migration path built into 3.4.0 was removed from 3.4.1. Somehow this left |
| 6 |
the kde-3.4.0 ebuild hanging around as a kind of ghost even though all the |
| 7 |
individual kde packages updated to 3.4.1. |
| 8 |
|
| 9 |
Running "emerge -C kde" didn't remove any actual kde packages, but it did |
| 10 |
clear the blockage and has allowed "emerge -u world" to proceed as it should. |
| 11 |
|
| 12 |
|
| 13 |
On July 9, 2005 04:53 pm Toby Cubitt was like: |
| 14 |
> On Sat, Jul 09, 2005 at 02:41:11PM -0700, Robert Persson wrote: |
| 15 |
> > A couple of weeks ago I added all the kde-3.4.1 packages to |
| 16 |
> > package.keywords and then ran emerge -u world and everything updated and |
| 17 |
> > ran fine. |
| 18 |
> > |
| 19 |
> > Today I tried to emerge -u world and I got |
| 20 |
> > |
| 21 |
> > [blocks B ] =kde-base/kdeartwork-icewm-themes-3.4* (is blocking |
| 22 |
> > kde-base/kdeartwork-3.4.1) |
| 23 |
> > ... blah blah blah ... |
| 24 |
> > [blocks B ] =kde-base/renamedlg-images-3.4* (is blocking |
| 25 |
> > kde-base/kdeaddons-3.4.1) |
| 26 |
> > |
| 27 |
> > for about 150 kde packages altogether. |
| 28 |
> > |
| 29 |
> > equery tells me that I have version 3.4.1 of each individual kde package |
| 30 |
> > installed, but that I have version 3.4.0 of kde itself and that I don't |
| 31 |
> > have kdeartwork, kdeaddons, kdebase etc. installed. |
| 32 |
> > |
| 33 |
> > How did I get in this mess and how (without recompiling all of kde) do I |
| 34 |
> > get out of it? |
| 35 |
> |
| 36 |
> I had a similar problem with upgrading when 3.4 was unmasked. The problem |
| 37 |
> is moving from the old monolithic ebuilds to the new split ones. I believe |
| 38 |
> it's because you are trying to install both split and unsplit ebuilds that |
| 39 |
> provide some of the same programs. |
| 40 |
> |
| 41 |
> My solution to sort out the mess was to unmerge all the monolithic kde |
| 42 |
> ebuilds, and then emerge the stuff I wanted (kdebase-startkde is the split |
| 43 |
> ebuild that provides the basic stuff like the window manager, though even |
| 44 |
> that isn't necessary if you only want to run some kde apps and not the full |
| 45 |
> kaboodle). |
| 46 |
> |
| 47 |
> It sounds like you might already have the new split ebuilds installed, so |
| 48 |
> you might just need to remove the monolithic ones from your world file, or |
| 49 |
> possibly unmerge them if they're still around. Of course, that assumes you |
| 50 |
> want to use the split ebuilds. |
| 51 |
> |
| 52 |
> If you haven't read it already, the How-To at |
| 53 |
> |
| 54 |
> http://gentoo-wiki.com/HOWTO_Update_KDE_3.3_to_KDE_3.4 |
| 55 |
> |
| 56 |
> is helpful. A bit of research with the online package database to work out |
| 57 |
> which ebuilds are the split ones, which the monolithic ones, and which ones |
| 58 |
> you actually want should sort you out. |
| 59 |
|
| 60 |
-- |
| 61 |
Robert Persson |
| 62 |
|
| 63 |
"Don't use nuclear weapons to troubleshoot faults." |
| 64 |
(US Air Force Instruction 91-111, 1 Oct 1997) |
| 65 |
|
| 66 |
-- |
| 67 |
gentoo-user@g.o mailing list |
Archives