Ian Jackson writes ("Re: [pkg-gnupg-maint] Bug#868550: reprepro seems to provide a repro"): > Here's the stderr output from one of the tests: > > + gpg --detach-sign --armor -u 39B13D8A > /home/ian/things/Dgit/dgit/tests/tmp/debpolicy-quilt-gbp/example/.git/dgit/tag.tmp > gpg: WARNING: unsafe permissions on homedir > '/home/ian/things/Dgit/dgit/tests/tmp/debpolicy-quilt-gbp/gnupg' > gpg: agent invoked successfully, but... > gpg: can't connect to the agent: IPC connect call failed > gpg: skipped "39B13D8A": No secret key > gpg: signing failed: No secret key > WARNING - GNUPG FAILED 2 - STUNT GNUPG --detach-sign --armor -u 39B13D8A > /home/ian/things/Dgit/dgit/tests/tmp/debpolicy-quilt-gbp/example/.git/dgit/tag.tmp
Corresponding AGENT.log: 2018-01-07 11:16:58 gpg-agent[6039] gpg-agent (GnuPG) 2.1.18 started 2018-01-07 11:19:39 gpg-agent[15119] gpg-agent (GnuPG) 2.1.18 started 2018-01-07 11:19:39 gpg-agent[15119] SIGTERM received - shutting down ... 2018-01-07 11:19:39 gpg-agent[15119] gpg-agent (GnuPG) 2.1.18 stopped 2018-01-07 11:20:39 gpg-agent[4484] gpg-agent (GnuPG) 2.1.18 started 2018-01-07 11:21:44 gpg-agent[4484] SIGTERM received - shutting down ... 2018-01-07 11:21:44 gpg-agent[4484] gpg-agent (GnuPG) 2.1.18 stopped I don't know who is sending it SIGTERM. My test suite doesn't send signals at all. But I couldn't rule out that it's one of the programs I am calling that calls gpg. If that were the case then presuably it would be killing the whole process group. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.