On Thursday, 14 October 2021 19:16:46 CEST Martin Steigerwald wrote: > > The best way to do that is not using *dist*-upgrade but the > > normal/safe- upgrade method ... > > Sometimes dist upgrade might be necessary as new packages are introduced > or old ones are removed. Trying dist upgrade also often gives a good > indication whether the builds are complete. IME it's *rarely* needed. Normally aptitude safe-upgrade installs and removes packages as needed. There is a common (?) misconception that it doesn't do that. What it does not, is remove packages that are marked as *manually* installed because that indicates that you (apparently) had a reason to explicitly install it. If "aptitude search '~i!~M'" returns (many) packages that you don't think should be marked as manually installed, that indicates that the 'state' of those packages are probably wrong. With "aptitude markauto <pkg>" or "apt-mark auto <pkg>" you can change that. HTH, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.