On Wednesday 10 February 2010 12:32:11 Helmut Jarausch wrote: > On 10 Feb, Alan McKinnon wrote: > > On Wednesday 10 February 2010 10:36:35 Helmut Jarausch wrote: > >> Hi, > >> > >> has anybody a recipe on this upgrade hell each time KDE release a new > >> version? > >> This time existing KDE-4.3.5 packages block KDE-4.4 packages though they > >> go to different slots. > >> Even portage-2.2_rc62 is unable to cope with that. > > > > Remove ALL version-specific information for kde entries from world. > > There are no specific version of kde in world > > > Don't mix and match -meta packages and sets. > > What do you mean by that? I don't think I have any kde-sets here > > # emerge --list-sets > downgrade > installed > live-rebuild > module-rebuild > preserved-rebuild > security > selected > system > unavailable > world > > > Beware of kde-misc entries - often times they have depends on the old > > SLOT and pull in conflicts. These ebuilds are not as maintained as the > > kdebase ones, same with the apps themselves.
In general terms, portage knows you have package A that must stay at v4.3.5 and you want to upgrade it (or more likely something that depends on it) to v4.4. It's telling you "I can't/won't do that". Please post the portage output for the blockers that portage won't resolve (not everything, that will be about 5000 lines) plus the command you are running if it's not "emerge -avuND world". Also, are you aware that as of yesterday, KDE-4.4 was still hard masked in $PORTDIR/profiles/package.mask? It may have been removed meanwhile since my last sync. And what do you have related to kde in your own /etc/portage/package* ? -- alan dot mckinnon at gmail dot com
