Comment 6 for bug 1992513

I'm going to set this to Won't Fix because that seems to be an important part of the solver logic, and the workarounds - running upgrade first, or using ubuntu-drivers - are easy to do and the potential for regression significantly outweighs them.

This will get solved eventually by a nicer solver (a proper optimization solver) sure, if we make it there. Lots of caveats because I'm not that clever that I want to write a competitive partial weighted maxsat or linear programming solver, so end up reusing libraries, and neither z3 nor clasp are exactly optimal (also figuring out how to get them to explain uninstallability is hard).

On the other hand, I am also exploring preventing the solver (both old and new) from removing packages due to Conflicts, so removals can only happen as part of a dist-upgrade or an explicit removal request, to further reduce issues with people breaking their systems by accidentally removing half of it (caveats as to the scope with manually vs automatically installed packages, and whether packages are not needed anymore are to be).