From: Justus Winter <justus@gnupg.org>
To: David Bremner <david@tethera.net>
Cc: notmuch@freelists.org, notmuch@notmuchmail.org
Subject: Re: [Bug] lingering gpg-agents from test suite
Date: Mon, 15 May 2017 09:44:31 +0200 [thread overview]
Message-ID: <871srqpns0.fsf@europa.jade-hamburg.de> (raw)
In-Reply-To: <8737c7zfmp.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
David Bremner <david@tethera.net> writes:
> Thanks to changes in gnupg 2.1.20, the agent started by the notmuch test
> suite is no longer killed by deleting the home directory.
>
> So yay, we get to adapt to changes in gnupg, again.
>
> See also
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862093
where you write:
> As of 2.1.20, removing $GNUPGHOME is no longer enough for gpg-agent to
> shut itself down. It seems that removing the directory
> /run/user/gnupg/d.$hash is enough to trigger the shutdown.
>
> I'm not sure the underlying cause; perhaps the change to use /run/user
> for non-standard homedirs (which I generally think is sensible) has
> this as a side-effect.
What triggers the automatic shutdown is the removal of the socket.
2.1.20 creates the so-called socket directory automatically (if it finds
/**/run/user).
> The main practical difficulty for me is that this makes it harder for
> test suites using gnupg to work across multiple gpg versions and
> multiple environments. I suppose I'll have to see how far back
> "gpgconf --kill all" is supported.
Yes, please try to do 'gpgconf --kill all' and ignore the exit status.
Justus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-05-15 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 14:18 [Bug] lingering gpg-agents from test suite David Bremner
2017-05-15 7:44 ` Justus Winter [this message]
2017-05-15 8:30 ` Tomi Ollila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871srqpns0.fsf@europa.jade-hamburg.de \
--to=justus@gnupg.org \
--cc=david@tethera.net \
--cc=notmuch@freelists.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).