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

Daniel Kahn Gillmor dkg at fifthhorseman.net
Tue Jul 5 20:28:50 UTC 2016

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 in
> 2.1.13 the socket path used to connect to dirmngr was moved.
> Would it be a good idea to add a 'Breaks: dirmngr (<< 2.13)' to gnupg
> to ensure this doesn't happen?

With the change to the socket locations, I'm not convinced that gnupg
actually Breaks: dirmngr any more than dirmngr Breaks: gnupg.  And since
it's only a Recommends (not a stronger Depends) it's unclear what the
right thing to do is.

You'll note that 2.1.13-5 now has tighter versioned Recommends: between
both gnupg and dirmngr (which i plan to keep going forward), so
hopefully that's sufficient to point out that these things need to
grouped together.


More information about the pkg-gnupg-maint mailing list