Branko Čibej <br...@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. -- Philip
