# emerge --depclean * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence, it is often necessary to run `emerge --update * --newuse --deep @world` prior to depclean. ================ The command "emerge --update --newuse --deep @world" was split on two lines I suggest to write it on one line. Users can use gpm and will not have to retype it and it is better to read. ================ * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence, it is often necessary to run * emerge --update --newuse --deep @world * prior to depclean. Reproducible: Always
Created attachment 360308 [details, diff] [PATCH] Fixes the bug I agree with you and have fixed the issue. Please file a new bug if you discover other examples of this.
This is fixed in git as ab02c3fd788da6cc36188cdbee62a2b22bbc2474.
released in portage-2.2.11
