On 15/08/2014 09:49, Сергей wrote: > sergey-pc sergey # emerge --depclean -a > > Calculating dependencies... done! >>>> No packages selected for removal by depclean >>>> To see reverse dependencies, use --verbose > Packages installed: 896 > Packages in world: 92 > Packages in system: 44 > Required packages: 896 > Number removed: 0 > sergey-pc sergey # emerge --depclean -a > > Calculating dependencies... done! >>>> Calculating removal order... > >>>> These are the packages that would be unmerged: > > > !!! 'app-editors/nano' (virtual/editor) is part of your system profile. > !!! Unmerging it may be damaging to your system. > > > app-editors/nano > selected: 2.3.2 > protected: none > omitted: none > > All selected packages: app-editors/nano-2.3.2 > >>>> 'Selected' packages are slated for removal. >>>> 'Protected' and 'omitted' packages will not be removed. > > Would you like to unmerge these packages? [Yes/No] > > NOTHING had changed between running these two commands. So, sometimes > depclean wants to remove nano, sometimes it doesn't. > If I look at emerge -pv --depclean, that's what I see: > If it removes nano: > sys-apps/ed-1.6 pulled in by: > app-text/texlive-core-2012-r1 requires sys-apps/ed > virtual/editor-0 requires sys-apps/ed > If it keeps nano: > app-editors/nano-2.3.2 pulled in by: > virtual/editor-0 requires app-editors/nano > > I have removed "ed" because I don't use it, but I think, depclean > should behave more exact. For example, say "Two different packages > provide *bla-bla* which is needed by installed virtual/*bla*"... > > Should I file a bug about this?
This could be part of the whole undeterminate behaviour of recent portage that shows up with --backtrack being too small? I agree that -depclean must be exact and no matter what code path is selected the results must always be identical on every run. So filing a bug seems warranted -- Alan McKinnon alan.mckin...@gmail.com
