Your quoting style is terrible...! On Saturday 24 June 2006 17:25, James wrote: > > > > Unmerge what you don't need or remerge (after emerging kde 3.5) what > > > > you still need. When you are done with that the above command should > > > > give no output and any files still in /usr/kde/3.2 - 3.4 can be > > > > safely deleted since they belong to no package. Pay attention to what > > > > you do though. A revdep-rebuild before this step will probably take > > > > care of most of this.
Here I was talking about cleaning out the cruft that third party applications that do not belong to KDE may leave behind after you have removed KDE from an old slot. This has nothing to do with the problems below. It is relevant when you are done upgrading kde and not before. [SNIP] > Well, something is messed up. I still get many many blocks: > > [blocks B ] =kde-base/kdepim-3.5* (is blocking > kde-base/libkpgp-3.5.0-r1) [SNIP] > [blocks B ] =kde-base/kdegraphics-3.5* > (is blocking kde-base/kamera-3.5.2) > I after deleting everything. I unmerge everthing (KDE) I thought: > 467 emerge --unmerge kde-base/kdewebdev > 468 emerge --unmerge kde-base/kdeadmin > 470 emerge --unmerge kde-base/kdemultimedia > 471 emerge --unmerge kde-base/kdepim > 472 emerge --unmerge kde-base/kdeutils > 475 emerge --unmerge kde-base/kdetoys > 477 emerge --unmerge kde-base/kdegraphics > 480 emerge --unmerge kde-base/kdenetwork > <snip> > but they are still blocking? Did you unmerge kde? It depends on the monolithic packages above. # emerge --unmerge kde > I tried revdep-rebuild > emerge --rsync and > env-update && source /etc/profile && etc-update && > update-eix && eupdatedb That's pretty pointless at the moment. When you don't know what is pulling something in you should add --tree to the emerge command. -- Bo Andresen
Description: PGP signature