On Sun, Oct 22, 2017 at 12:04:01AM -0000, Julian Andres Klode wrote: > Because let's face it: If A suggests B, B provides or modifies > functionality for A, so removing B might just break your use case of A.
That is absolutely not apt's responsibility to handle, when the admin has never indicated to the package manager that they want to keep B; and is nothing when weighed against the asymmetry that causes package cruft to be kept around on every user's systems after upgrade. A user who discovers after autoremovals that she wants B installed can install B from the archive. But a user who just wants no-longer-needed packages to be autoremoved has no reasonable way to get this - because that's what 'autoremove' is supposed to imply already, but it doesn't actually deliver unless you track down this non-obvious apt setting and tweak your config. If 'apt install A=1; apt install A=2; apt autoremove --purge' gives different results than 'apt install A=2; apt autoremove --purge', then that is a bug. Sometimes it's a bug in a package. In this case, it's a bug in the package manager. The current behavior is not a sensible default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725861 Title: APT::AutoRemove::SuggestsImportant "false" should be the default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1725861/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
