Le 28 juillet 2018, Michael Gilbert a écrit:
> control: tag -1 moreinfo
>
> On Sat, Jul 28, 2018 at 3:13 AM, Remi Vanicat wrote:
>> Package: chromium
>> Version: 68.0.3440.75-1~deb9u1
> [...]
>> Upgrading chromium on a sid box failed :
>
> What was the precise command executed that caused this?
sudo apt upgrade
>
>> -- System Information:
>> Debian Release: buster/sid
>> APT prefers oldstable-updates
>> APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'),
>> (500, 'oldstable'), (150, 'unstable'), (120, 'experimental')
>
> Your configuration is one that favors stable over unstable, even so
> 68.0.3440.75-1 (unstable) should have been chosen over
> 68.0.3440.75-1~deb9u1 (stable) based on dpkg's sorting algorithm.
I disagree. 67.0.3396.87-1 was installed (from testing), there was two
version for upgrading the package (68.0.3440.75-1 and
68.0.3440.75-1~deb9u1), one with priority 150, the other with priority
500, the algorithm choose the latter :
$ apt-cache policy chromium
-~
chromium:
Installed: 68.0.3440.75-1~deb9u1
Candidate: 68.0.3440.75-1~deb9u1
Version table:
68.0.3440.75-2 150
150 http://ftp.fr.debian.org/debian sid/main amd64 Packages
*** 68.0.3440.75-1~deb9u1 500
500 http://security.debian.org stable/updates/main amd64 Packages
100 /var/lib/dpkg/status
67.0.3396.87-1 500
500 http://ftp.fr.debian.org/debian testing/main amd64 Packages
63.0.3239.84-1~deb9u1 500
500 http://ftp.fr.debian.org/debian stable/main amd64 Packages
57.0.2987.98-1~deb8u1 500
500 http://security.debian.org jessie/updates/main amd64 Packages
>
> How specifically would someone else reproduce what you did?
Install the version currently in testing (67.0.3396.87-1) upgrade to the
version in stable/security.
Well, one can assert that the problem concern the version in testing and
close this bug once the version in unstable migrate.
Thanks.
--
Rémi Vanicat
