at bottom :-
On 08/01/2017, intrigeri wrote:
> shirish शिरीष:
>> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>
>> gpg: keyserver receive failed: No keyserver available
>
>> Tried it multiple times but get the above failure.
>
> [...]
>
>> Any ideas what I need to do next ?
>
> Add a "de
shirish शिरीष:
> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
> gpg: keyserver receive failed: No keyserver available
> Tried it multiple times but get the above failure.
[...]
> Any ideas what I need to do next ?
Add a "debug-all" line in ~/.gnupg/dirmngr.conf, restart
dirmngr.socket
at bottom :-
On 08/01/2017, intrigeri wrote:
> shirish शिरीष:
>> in-line :-
>
>> On 07/01/2017, Daniel Kahn Gillmor wrote:
>>> Have you restarted dirmngr since the upgrade?
>
>> how do I restart it ?
>
> systemctl --user restart dirmngr.socket
>
> :)
>
Did that and get the following -
─[$] sys
shirish शिरीष:
> in-line :-
> On 07/01/2017, Daniel Kahn Gillmor wrote:
>> Have you restarted dirmngr since the upgrade?
> how do I restart it ?
systemctl --user restart dirmngr.socket
:)
in-line :-
On 07/01/2017, Daniel Kahn Gillmor wrote:
> On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
>> But issue is still continuing -
>>
>> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>>
>> [4:22:18]
>> gpg: keyserver receive failed: No keyserver available
>>
>> I tried multi
On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
> But issue is still continuing -
>
> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>
> [4:22:18]
> gpg: keyserver receive failed: No keyserver available
>
> I tried multiple times with various other keys but didn't succeed.
Have you r
Hi all,
I was able to get the new version -
─[$] sudo aptitude install gnupg=2.1.17-3 dirmngr=2.1.17-3
gpgv=2.1.17-3 gnupg-agent=2.1.17-3 gpgsm=2.1.17-3 scdaemon=2.1.17-3 -y
Installed it perfectly
─[$] apt-cache policy gnupg
[4:19:09]
gnupg:
Installed: 2.1.17-3
Candidate: 2.1.17-3
Versio
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
>
at bottom :-
On 07/01/2017, Daniel Kahn Gillmor wrote:
> On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote:
>> I have no place in the topic of this bug, but I installed the patches
>> you provided on January 5th onto my Debian Testing system. I would like
>> to notify you that gpgv2 depends
On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote:
> I have no place in the topic of this bug, but I installed the patches
> you provided on January 5th onto my Debian Testing system. I would like
> to notify you that gpgv2 depends on gpgv version 2.1.17-3 or greater,
> which is not provide
Hi,
Werner Koch:
> On Mon, 2 Jan 2017 13:46, intrig...@debian.org said:
>> ... which is expected if querying 127.0.0.1, that doesn't support
>> SRV records.
> The question is whether we should gracefully handle this failure and
> return 0 records found (as done < 2.1.17)?
I lack the background
On Mon, 2 Jan 2017 13:46, intrig...@debian.org said:
> ... which is expected if querying 127.0.0.1, that doesn't support
> SRV records.
The question is whether we should gracefully handle this failure and
return 0 records found (as done < 2.1.17)?
> Jan 02 13:37:57 dirmngr[8281]: DBG: dns:
>
12 matches
Mail list logo
