> -----Original Message----- > From: Neil Bothwick [mailto:[EMAIL PROTECTED] > > As you have determined the files no longer belong to a package, it is > quite safe to remove them. >
This is a small thing but here is the current result from ->revdep-rebuild --pretend Configuring search environment for revdep-rebuild Checking reverse dependencies... [lines deleted....] Checking dynamic linking consistency... broken /opt/blackdown-jdk-1.4.2.03/jre/lib/i386/libjsoundalsa.so (requires libasound.so.2) done. (/root/.revdep-rebuild.3_rebuild) [lines deleted...] All prepared. Starting rebuild... emerge --oneshot --pretend =dev-java/blackdown-jdk-1.4.2.03-r12 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-java/blackdown-jdk-1.4.2.03-r12 Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild. This happens over and over again. The package blackdown-jdk is not in world and according to equerry depends blackdown-jdk a lot of other packages depend on it. I unmerged it and did an emerge --update --newuse --deep world, followed by an emerge --depclean, and still revdep-rebuild complains about the broken link, reemerges the package with --oneshot option and continues to do that after each revdep-rebuild. The library libasound.so.2 is not on the system. This looks like a bug...and yes it is: http://bugs.gentoo.org/show_bug.cgi?id=83852 -- Valmor -- [email protected] mailing list
