On Sun, Aug 19, 2018 at 09:19:57PM +0200, Olaf van der Spek wrote: > So after X attempts the culprit is found: adminer > Wouldn't been so much easier if apt told me right away. Just for the record: -o pkgProblemResolver::FixByInstall=0 can help in these situations. The "problem" here is that apt can avoid removing a bunch of packages if only it installs a few new ones and as new things tend to be less dangerous for not breaking usecases then removing things it does so. Every once in a while I wonder if we should make that the default for 'remove foo' actions, but then its less clear what 'install foo-' should do as behind the scenes remove/install are the same code, they just flip the default interpretation of package names without an explicit action specified (= what Julian hinted at with '-' and '+' after a package name) and these kinds of hidden differences can end in a nightmare. The lesson is as it is so often the case: choose either as default but regardless the choice someone will be unhappy. Best regards David Kalnischkies, who remembers writing that code initially to fix a bunch of upgrade problems for a Debian release a couple years ago
Attachment:
signature.asc
Description: PGP signature