On Wed 2016-10-12 04:01:42 -0400, Vincent Danjean wrote: > Package: gnupg1 > Version: 1.4.21-1+b1 > Followup-For: Bug #840452 > > There is also a problem in gnupg1-l10n (arch: all) that > has currently: > Enhances: gnupg1 (= 1.4.21-1) > while only gnupg1 1.4.21-1+b1 is available. > > This situation leads my system to propose me to remove > gnupg1-l10n: > vdanjean@eyak:~$ LC_ALL=C sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following package was automatically installed and is no longer required: > gnupg1-l10n > Use 'sudo apt autoremove' to remove it. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > vdanjean@eyak:~$ apt-cache policy gnupg1-l10n gnupg1 > gnupg1-l10n: > Installé : 1.4.21-1 > Candidat : 1.4.21-1 > Table de version : > *** 1.4.21-1 500 > 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages > 500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages > 100 /var/lib/dpkg/status > gnupg1: > Installé : 1.4.21-1+b1 > Candidat : 1.4.21-1+b1 > Table de version : > *** 1.4.21-1+b1 500 > 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages > 500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages > 100 /var/lib/dpkg/status
indeed, that's annoying. however, i think that when 1.4.21-2 gets
uploaded [0] with the slightly looser Recommends: from gnupg1 to
gnupg1-l10n, apt will not consider gnupg1-l10n to be abandoned
("auto-installed") from a dependency viewpoint:
[0]
https://anonscm.debian.org/git/pkg-gnupg/gnupg1.git/commit/?id=b4b610ef8c241c23717ec7ccc423d3811e07741b
Thanks for checking in and reporting back. Please let me know if you
think this fix isn't going to resolve your view of the problem for some
reason.
--dkg
signature.asc
Description: PGP signature
