Re: [PATCH 2/2] exit lingering gpg agents at the end of relevant tests

2017-05-25 Thread David Bremner
David Bremner writes: > Tomi Ollila writes: > >> Since gnupg 2.1.20, gpg-agent no longer shut itself down when >> $GNUPGHOME directory is removed. >> >> Add exit hooks to the test modules which execute `gpgconf --kill all` >> > > Did you test this on some

Re: [PATCH 2/2] exit lingering gpg agents at the end of relevant tests

2017-05-24 Thread David Bremner
Tomi Ollila writes: > Since gnupg 2.1.20, gpg-agent no longer shut itself down when > $GNUPGHOME directory is removed. > > Add exit hooks to the test modules which execute `gpgconf --kill all` > Did you test this on some machines with old gpg (1.x)? I think I don't have easy

Re: [PATCH 2/2] exit lingering gpg agents at the end of relevant tests

2017-05-23 Thread Daniel Kahn Gillmor
On Tue 2017-05-23 21:54:25 +0300, Tomi Ollila wrote: > Since gnupg 2.1.20, gpg-agent no longer shut itself down when > $GNUPGHOME directory is removed. > > Add exit hooks to the test modules which execute `gpgconf --kill all` > > Add exit hooks to execute `gpgconf --kill all` in the modules that >

[PATCH 2/2] exit lingering gpg agents at the end of relevant tests

2017-05-23 Thread Tomi Ollila
Since gnupg 2.1.20, gpg-agent no longer shut itself down when $GNUPGHOME directory is removed. Add exit hooks to the test modules which execute `gpgconf --kill all` Add exit hooks to execute `gpgconf --kill all` in the modules that create $GNUPGHOME for gpg to work with. --- test/T350-crypto.sh