Bug#829750: [pkg-gnupg-maint] Bug#829750: gnupg2: 2.1.13 can't connect to dirmngr from 2.1.11

2016-07-05 Thread Daniel Kahn Gillmor
Version: 2.1.13-5 Hi James-- On Tue 2016-07-05 14:41:02 -0400, James Cowgill wrote: > I just upgraded to the experimental version of gnupg2 to try it out, > but immediately usage of --recv-keys stopped working. I found that this > was because I was still using dirmngr 2.1.11-7 from unstable and

Bug#829750: [pkg-gnupg-maint] Bug#829750: gnupg2: 2.1.13 can't connect to dirmngr from 2.1.11

2016-07-05 Thread Werner Koch
On Tue, 5 Jul 2016 20:41, jcowg...@debian.org said: > Would it be a good idea to add a 'Breaks: dirmngr (<< 2.13)' to gnupg > to ensure this doesn't happen? Most thinks keep on working with a running old dirmngr or gpg-agent. But it is not a good idea to do this. gpg prints a warning if it

Bug#829750: gnupg2: 2.1.13 can't connect to dirmngr from 2.1.11

2016-07-05 Thread James Cowgill
Package: gnupg2 Version: 2.1.13-4 Severity: normal Hi, I just upgraded to the experimental version of gnupg2 to try it out, but immediately usage of --recv-keys stopped working. I found that this was because I was still using dirmngr 2.1.11-7 from unstable and in 2.1.13 the socket path used to