[pkg-gnupg-maint] Bug#849845: Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[Daniel Kahn Gillmor]

On Fri 2017-01-06 14:47:46 -0500, shirish शिरीष wrote:
> I can confirm Jaden's findings. Perhaps the content hasn't reached his
> mirror yet. It's same thing at my end. I just updated to see if the
> new version has come up at my end. (not even in sid/unstable)
>
> [$] apt-cache policy gpgv
>                                                              [1:14:58]
> gpgv:
>   Installed: 2.1.17-2
>   Candidate: 2.1.17-2
>   Version table:
>  *** 2.1.17-2 600
>         600 http://httpredir.debian.org/debian stretch/main amd64 Packages
>           1 http://httpredir.debian.org/debian unstable/main amd64 Packages
>         100 /var/lib/dpkg/status
>
> Timing is in IST. My last apt update run was about 5 minutes ago and I
> do know that the update mirrors are hit every 4 hours or more, so
> maybe in the next 4-8 hours the new binary might be available.

1 dkg at alice:~$ rmadison -a amd64 gpgv
gpgv       | 1.4.12-7+deb7u7 | oldstable       | amd64
gpgv       | 1.4.18-7+deb8u3 | stable          | amd64
gpgv       | 2.1.17-2        | testing         | amd64
gpgv       | 2.1.17-3        | buildd-unstable | amd64
gpgv       | 2.1.17-3        | unstable        | amd64
0 dkg at alice:~$ 

I'm not sure what to make of this confusion, but it seems to be related
to the mirror network, not to the gnupg2 source package.  If it's still
a confusion or a problem for you in the next day, this might need to be
kicked over to the mirror network or the archive managers.

       --dkg