Hello, I've been updating a kde3 workstation to kde4 off and on for a few days now. KDE4 is installed and seem to work, no extensive testing yet.
However, when I run revdep-rebuild, it complains about numerous kde3 based packages. Most, if not all had the kde4 equivalent packages installed. So I just manually deleted the list of kde3.5.x based packages. <snip> So a few more manual passes of removing the offending kde-3.5.x packages and I'm down to this list of packages that revdep-rebuild wants to rebuild: I get the list from revdep-rebuild, research if I want the packages and then clean out the (crufted) revdep-rebuild list and continue until I'm down to these packages: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] sys-fs/device-mapper-1.02.24-r1 USE="(-selinux)" [ebuild U ] media-libs/lcms-1.18-r1 [1.17] [ebuild R ] sys-fs/cryptsetup-1.0.6-r2 [ebuild R ] net-libs/xulrunner-1.8.1.19 [ebuild U ] net-libs/xulrunner-1.9.1.4 [1.9.0.7] USE="alsa%* python%* -debug% -sqlite% -startup-notification*" [ebuild R ] sys-apps/hal-0.5.12_rc1-r8 So far so good. I did not actually allow revdep-rebuild to complete, as I want all vestiges of kde3 and other cruft gone. Now I have a list I can focus on, except, I'm confused about device-mapper, ,cryptsetup, and xulrunner as my research suggest device-mapper is not needed, but it is being call by: [ Searching for packages depending on device-mapper... ] sys-fs/cryptsetup-1.0.6-r2 (>=sys-fs/device-mapper-1.00.07-r1) Research suggests that I can install lvm2 and be done with that? But it first wants to call back device-mapper? Now, guidance here is appreciated. James
