At Wed, 03 Dec 2008 18:32:24 -0500 "Michael P. Soulier" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]:~$ emerge --pretend --depclean > > *** WARNING *** Depclean may break link level dependencies. Thus, it is > *** WARNING *** recommended to use a tool such as `revdep-rebuild` (from > *** WARNING *** app-portage/gentoolkit) in order to detect such breakage. > *** WARNING *** > *** WARNING *** Also study the list of packages to be cleaned for any obvious > *** WARNING *** mistakes. Packages that are part of the world set will always > *** WARNING *** be kept. They can be manually added to this set with > *** WARNING *** `emerge --noreplace <atom>`. Packages that are listed in > *** WARNING *** package.provided (see portage(5)) will be removed by > *** WARNING *** depclean, even if they are part of the world set. > *** WARNING *** > *** WARNING *** As a safety measure, depclean will not remove any packages > *** WARNING *** unless *all* required dependencies have been resolved. As a > *** WARNING *** consequence, it is often necessary to run > *** WARNING *** `emerge --update --newuse --deep world` prior to depclean. > > Calculating dependencies... done! > > Dependencies could not be completely resolved due to > the following required packages not being installed: > >>=virtual/perl-Compress-Zlib-1.14 required by dev-perl/Archive-Zip-1.23 > virtual/perl-ExtUtils-CBuilder required by perl-core/File-Spec-3.27.01 > > Have you forgotten to run `emerge --update --newuse --deep world` prior to > depclean? It may be necessary to manually uninstall packages that no longer > exist in the portage tree since it may not be possible to satisfy their > dependencies. Also, be aware of the --with-bdeps option that is documented > in `man emerge`. > > In running emerge --update --newuse --deep world, it yields nothing. Did you try emerge --update --newuse --deep --with-bdeps=y world as hinted at by the above msg? allan
