[Pkg-privacy-maintainers] Bug#827311: Bug#827311: Bug#827311: parcimonie can't find the keyserver for gpg2

[intrigeri]

Daniel Kahn Gillmor wrote (22 Jun 2016 19:46:16 GMT) :
> On Wed 2016-06-22 12:44:01 -0400, Sven Bartscher wrote:
>> Do I really need to configure the keyserver in the dirmngr.conf? If so,
>> that would be a bit inconvenient, as gpg2 itself is fine with having
>> the keyserver configured in gpg.conf.

> in 2.1.9, gpg started deprecating that option.  From gnupg's NEWS file:

>   * dirmngr: Add option --keyserver.  Deprecate that option for gpg.

> But the error you originally cited was a parcimonie error, not a gpg
> error, right?  i don't know enough about parcimonie to know why it might
> think there are different rules for the different versions.

> I recommend that you put your preferred keyserver into dirmngr.conf,
> even if it duplicates the entry in gpg.conf.  does that solve the
> parcimonie issue?

Oops, I missed that email and released parcimonie 0.10.2 that allows
keyserver being defined in gpg.conf *only*, even when using GnuPG 2.x.

After reading what Daniel wrote, it looks like I should revert this
change, shouldn't I?

Cheers,
-- 
intrigeri