As I wrote to Sven on debian-user, there are really two bugs here:
(1) aptitude, at least on my machine, takes way too long to compute
a dependency solution in this case.
(2) aptitude produces a solution that still has broken dependencies.
I don't know about (1) yet, although it's suggestive that a rendering
of the search tree has lots of identically-shaped branches, but I have a
diagnosis for (2): the root of this problem is yet another interaction
between the dependency solver and the removal of unused packages. :-(
DEBUG aptitude.apt.cache - aptitudeDepCache::sweep(): Removing
kdebase-bin-kde3: it is unused.
(...)
TRACE aptitude.resolver.search - Trying to resolve kdebase-runtime 4:4.2.2-1 ->
{kdebase-runtime-bin-kde4 4:4.2.2-1} by installing kdebase-runtime-bin-kde4
4:4.2.2-1
DEBUG aptitude.apt.cache - aptitudeDepCache::sweep(): Cancelling the removal of
kdebase-bin-kde3: it is no longer unused.
I'm not sure yet which package caused kdebase-bin-kde3 to become
"used", but this looks like a generic problem with the dependency
solver at first glance. (or maybe with that logic to reinstate
packages; this isn't the first time it's caused trouble)
Daniel
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
