[Pkg-gnupg-maint] Bug#769460: Bug#769460: gnupg2 2.1.0-1 --refresh-keys breaks with dirmngr < 2.1.0-1

[Daniel Kahn Gillmor]

Hi Sven--
On 11/13/2014 09:18 AM, Sven Hesse wrote:
>>From what I can figure out by googling, for gnupg 2.1, dirmngr is
> mandatory for --refresh-keys. Without it, that operation fails.
> 
> And it also doesn't seem to like dirmngr < 2.1.0-1 at all, again
> failing (with the error "IPC connect call failed").

thanks for the report, both here and on LWN :)

> I hadn't thought about checking for a higher version to dirmngr
> until dkg told me it recommends this version. Yes, with dirmngr
> 2.1.0-1, it works. Well, apart from an apparently known and fixed
> upstream bug that --refresh-keys fails with "Too many objects"
> (<http://web.archiveorange.com/archive/v/2TGPMrmEQ8Qf4Fpiwett>,
>  <https://bugs.g10code.com/gnupg/issue1755>).

yes, that's a separate issue.

> Not quite sure if something should be done about it. Set a hard
> dependency on dirmngr >= 2.1.0-1 instead of a recommendation?
> Add a conflicts dirmngr < 2.1.0-1? Or is it just a user error on
> my part?

These are the two main approaches i've considered as well, and i think
i'm leaning toward putting a Conflicts: dirmngr < 2.1.0~ on gnupg2, even
though it's not exactly correct.  a hard dependency would be too much (i
want to be able to have just gnupg2, without dirmngr at all on a pared
down machine)

Anyone else on the pkg-gnupg team have any other suggestions for how to
resolve this?

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20141113/ff6719f3/attachment.sig>