Known-bad candidate versions are not an upgrade option

If we have a negative dependency to deal with we prefer to install an
upgrade rather than remove the current version. That is why we split the
method rather explicitly in two in 57df273 but there is a case we didn't
react to: If we have seen the candidate before as a "satisfier" of this
negative dependency there is no point in trying to upgrade to it later
on. We keep that info by candidate discard if we can, but even if we
can't we can at least keep that info around locally.

This "fixes" (or would hide) the problem described in 04a020d as well as
you don't have to discard installations you never make.

0 files changed, 0 insertions, 0 deletions