Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=master 2020-07-02T16:57:11Z 2020-07-02T16:57:11Z David Kalnischkies david@kalnischkies.de 2020-06-19T11:58:35Z urn:sha1:cfd0172fb0eeb15b2e2427c0e11b2ec65f501839 If the package providing the given solution is tagged already for removal (or at least for "not installing") we can ignore this solution as a possibility as it is not one, which means we can avoid exploring the option and potentially forward the protected flag further if that helps in reducing the possibilities to a single one. 2020-07-02T16:57:11Z David Kalnischkies david@kalnischkies.de 2020-06-19T11:14:33Z urn:sha1:3e39efa31da463ca05016513835d9a5388f80f90 Marking a package for removal is fine if we know that we have to remove that package, but if we are in an alternative branch we might not go this route in the end and hence have a package pointlessly marked for removal which isn't questioned later on. We check if we are allowed to remove that package to avoid working on the positive dependencies if not, but we mark them for removal only after all the other dependencies are successfully resolved. In an ideal world we would let the problemResolver do its job on them, but the resolver might decide against doing the removal exploring another option like the next alternative, which might be a good idea, but is not the behaviour we had before, so that is the best we can do for now without changing the resolver drastically.