The reason it blocks is because you have other packages installed that depend 
on kde-base/kdebase. For example:  kde-base/kdepim and kde-base/kdenetwork
These are all part of the monolithic packages.

First you'll have to make a choice between monolithic (grouped) and segregated 
(split). Once you've made your choice you should unmerge all kde packages 
that belong to the type you don't want. You can recognize monolithic packages 
as they have a "kde-base/<packagename>-meta" replacement which use the split 
packages.

On Tuesday 01 November 2005 23:59, Hamish Marson wrote:
> Sebastian Redl wrote:
> > Hamish Marson wrote:
> >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> >>
> >> I have a problem with emerging kde... ever since going to 2005.0
> >> I get
> >
> > It seems that you have a few packages from the split ebuild version
> > of KDE installed. Since the grouped ebuilds and the split ebuilds
> > contain the same programs, they block each other.
> >
> > I recommed completely cleaning out everything from kde-base and
> > starting anew then. (I'd install the split ebuilds then, but it's
> > your call.)
>
> Yeah... I thought I'd already been that route once already... It would
> be nice to know why the system thinks it has kde-base (Grouped?)
> installed, when trying to unmerge it says that it isn't installed at
> all...
-- 
gentoo-amd64@g.o mailing list