That is a regression of sorts caused by a sleight of hand used to avoid another bug. The commit in question would be https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=446551c8ffd2c9cb9dcd707c94590e73009f7dd9 although the involved code changed in the mean time the general idea remains the same: We change the candidate (which we also do in another case: M-A:same version screws) which means later parts do not realize that there ever was a chance to upgrade the package.
That is a regression of sorts caused by a sleight of hand used to avoid another bug. The commit in question would be https:/ /anonscm. debian. org/cgit/ apt/apt. git/commit/ ?id=446551c8ffd 2c9cb9dcd707c94 590e73009f7dd9 although the involved code changed in the mean time the general idea remains the same: We change the candidate (which we also do in another case: M-A:same version screws) which means later parts do not realize that there ever was a chance to upgrade the package.
In other words: Not that easy to fix…