On Sun, Feb 1, 2009 at 3:07 PM, Daniel D Jones <ddjo...@riddlemaster.org> wrote: > On Sunday 01 February 2009 15:40:29 Norberto Bensa wrote: >> On Sun, Feb 1, 2009 at 1:38 PM, Daniel D Jones <ddjo...@riddlemaster.org> > wrote: >> > I have KDE 3.5 and 4.1 installed and am trying to upgrade to 4.2. I'm >> > getting the following: >> >> You'll need kde-3.5.10 (or kdebase-startkde at least) >> >> Look in the archives, a similar question was posted a few days ago. > > Thanks for your response. I did search the archives and did not find anything > relevant. I saw and read a thread where a block was occurring: > > <=kde-base/kdebase-startkde-3.5.10" is blocking kde-base/kdelibs-4.2.0 > > It wasn't clear to me that this was the same problem, since that block > referenced a 3.5.10 package and mine referenced a 3.5.9 package.
since the block is: <=kde-base/kdebase-startkde-3.5.10" is blocking kde-base/kdelibs-4.2.0 and 3.5.9 <= 3.5.10, then yes, the mail applies to you You'll need kdebase-startkde > 3.5.10 (3.5.10-r5 is available in portage) > However, upgrading to 3.5.10 raises another issue. For 3.5, I didn't install > the meta package, I installed the KDE base package: Uhm... Do you mean monolitich (base) vs. modules (meta)? > 3.5.10 is available under the meta package system but not under the KDE > package. Do I have to switch to the meta package to go to 3.5.10? (Without, > that is, manually unblocking lots and lots of packages.) Can I simply > install the meta package over the base package or will that create blocks or > other issues? I don't know. Perhaps another user can answer that question. I moved to modules as soon as it was made available. Regards, Norberto