Philip Martin wrote on Mon, 10 Jul 2017 14:06 +0100:
> Branko Čibej 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,
Branko Čibej 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
On 10.07.2017 12:37, Daniel Shahaf wrote:
> Daniel Shahaf wrote on Sun, 02 Jul 2017 04:36 +:
>> That error is from tools/dist/security/_gnupg.py. The error disappears when
>> I install that module via my OS packages, so I assume we should update our
>> import.
> Another issue: gnupg.py seems t
Daniel Shahaf wrote on Sun, 02 Jul 2017 04:36 +:
> That error is from tools/dist/security/_gnupg.py. The error disappears when
> I install that module via my OS packages, so I assume we should update our
> import.
Another issue: gnupg.py seems to only use gpg1 keyring files, so after running
_gnupg.py is used by release.py and by advisory.py (the confidential
pre-notification script).
I'm getting an error from it:
[[[
$ python2 tools/dist/release.py check-sigs --target=wc-of-dist 1.9.6
INFO:root:Checking 3 sig(s) in ./subversion-1.9.6.tar.bz2.asc
Exception in thread Thread-3:
Traceb
5 matches
Mail list logo