shiva ~ # emerge -pv --depclean *** WARNING *** --depclean is known to be broken. It is highly recommended *** WARNING *** that `emerge --update --newuse --deep world` be ran before *** WARNING *** commencing. However, using --depclean may still break link *** WARNING *** level consistency within your system. `revdep-rebuild` *** WARNING *** from app-portage/gentoolkit can help to detect breakage. *** WARNING *** *** WARNING *** Also study the list of packages to be cleaned for any *** WARNING *** obvious mistakes. Packages can be manually added to the *** WARNING *** world list by running `emerge --noreplace <atom>`. *** WARNING *** *** WARNING *** It is normal for packages that are masked or listed in package. provided *** WARNING *** to be removed by depclean. These are the most likely reasons t hat *** WARNING *** depclean will remove a package even though it is in the world o r system *** WARNING *** package set. In order to troubleshoot these types of problems, it is *** WARNING *** often helpful to look at the output of `grep -r <atom> /etc/por tage`. *** WARNING *** *** WARNING *** Make sure you have a backup. Calculating dependencies... done! Packages installed: 376 Packages in world: 77 Packages in system: 59 Unique package names: 376 Required packages: 382 Number to remove: 0
Thanks, this is fixed in svn r3446.
This has been released in 2.1_rc3-r5.
