From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: aidecode@aidecode.name
Subject: Re: Proposed fix for test failures due to long socket paths
Date: Tue, 21 Feb 2017 08:19:47 -0400 [thread overview]
Message-ID: <87y3wz4ty4.fsf@tethera.net> (raw)
In-Reply-To: <20170214214239.9330-1-david@tethera.net>
David Bremner <david@tethera.net> writes:
> Amadeusz Żołnowski found a bug in the test suite that causes gpg
> failures when the path of the test directory is sufficiently long.
> His current solution in Gentoo is to move the sockets into /tmp. It
> seems cleaner to enable gnupg's built in /run based short pathed
> sockets. As far as I know the gpgconf option used here is available
> in gnupg 2.1.13 and later. Amadeusz reported that the problem was
> "fixed" in Gentoo by downgrading gnupg to 2.1.15. So while I'm not
> 100% sure, it seems like a fix for very recent gnupg is all that is
> required. Testing of these patches with older gpg would be
> particularly welcome.
Pushed the series (with Tomi's changes) to release and master
d
prev parent reply other threads:[~2017-02-21 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:42 Proposed fix for test failures due to long socket paths David Bremner
2017-02-14 21:42 ` [PATCH 1/2] configure: add test for gpgconf --create-socketdir David Bremner
2017-02-14 22:02 ` David Bremner
2017-02-14 21:42 ` [PATCH 2/2] test: use gpgconf --create-socketdir if available David Bremner
2017-02-15 18:17 ` Daniel Kahn Gillmor
2017-02-15 18:59 ` David Bremner
2017-02-19 10:24 ` Tomi Ollila
2017-02-21 12:19 ` David Bremner [this message]
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=87y3wz4ty4.fsf@tethera.net \
--to=david@tethera.net \
--cc=aidecode@aidecode.name \
--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).