[Aptitude-devel] Bug#934541: aptitude: upgraded a package to experimental without notice, though SolutionCost has "safety" first

[Vincent Lefevre]

On 2020-02-24 09:45:46 +0100, Vincent Lefevre wrote:
> Control: found -1 0.8.12-1
> 
> This bug still occurs. During an upgrade last month:
> 
> Aptitude 0.8.12: log report
> Mon, Jan 27 2020 13:16:20 +0100
> [...]
> [UPGRADE] bash-completion:amd64 1:2.9-1 -> 1:2.10-1
> [UPGRADE] dict-wn:amd64 1:3.0-35 -> 1:3.0-36
> [UPGRADE] ksh:amd64 2020.0.0-2.1 -> 2020.0.0-4
> [UPGRADE] lzip:amd64 1.21-5 -> 1.21-6
> [UPGRADE] mksh:amd64 57-4 -> 57-5
> [UPGRADE] opera-stable:amd64 66.0.3515.36 -> 66.0.3515.44
> [UPGRADE] python-apt:amd64 1.8.5 -> 1.8.6
> [UPGRADE] python-apt-common:amd64 1.8.5 -> 1.9.5
> [UPGRADE] python3-apt:amd64 1.8.5 -> 1.8.6
> [UPGRADE] qpdf:amd64 9.1.0-1 -> 9.1.1-1
> 
> but python-apt-common comes from experimental:
[...]

And note that there is only an unversioned dependency from
python-apt and python3-apt to python-apt-common. Thus there
are 2 (possibly related) issues:

1. A bug in the resolver, which proposed the experimental version,
   though this was not requested by a dependency.

2. A missing warning about the upgrade of an unstable package to
   experimental.

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)