Philip Martin wrote on Mon, 10 Jul 2017 14:06 +0100:
> Branko Čibej <brane_at_apache.org> writes:
>
> > It works fine for me, and I only have a 'gpg' binary which is 'gpg2'.
> > The only issue is that 'release.py check-sigs' gets confused when a new
> > key is imported from the keyserver, and bails out; a second run, when
> > the key is already in my keyring, works fine.
>
> I get the same error as Daniel but an update to 0.4.1 from
> https://bitbucket.org/vinay.sajip/python-gnupg (the site mentioned in
> r1719107) makes things work. My system has gpg 2.1.18 as the only gpg
> installed.
In r1801492 you updated _gnupg.py to 0.4.1.
That seems to have fixed my problems. Before that revision, I was using
0.3.9 via OS packages, and with that set up, 'check-sigs' would only look
for public keys in gpg1 keyring files, not in gpg2 keybox files. I've
updated to r1801492 and removed the 0.3.9 OS version and the gpg1 binary
which was installed along with it, and now get-keys/check-sigs works.
Thanks!
Received on 2017-07-11 01:43:39 CEST