From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available
Date: Wed, 15 Feb 2017 13:17:47 -0500 [thread overview]
Message-ID: <87efyzl3n8.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <20170214214239.9330-3-david@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Tue 2017-02-14 16:42:39 -0500, David Bremner wrote:
> This enables the shortened socket pathes in /run or equivalent. The
> explicit call to gpgconf is needed for nonstandard GNUPGHOME settings.
For the current GnuPG 2.1.18, this pair of patches looks reasonable to
me, and it should indeed solve builds in deeply-nested paths.
That said, i currently consider this a workaround to a bug that should
really be fixed in GnuPG itself, as i noted on gnupg-users:
https://lists.gnupg.org/pipermail/gnupg-users/2017-February/057692.html
id:87k28rl6o8.fsf@alice.fifthhorseman.net
I'd love to not see this kind of workaround cruft pile up, because it
tends to cause problems in the future. is there a way that we can mark
this sort of thing for fairly prompt removal once it's fixed upstream?
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-02-15 18:17 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 [this message]
2017-02-15 18:59 ` David Bremner
2017-02-19 10:24 ` Tomi Ollila
2017-02-21 12:19 ` Proposed fix for test failures due to long socket paths David Bremner
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=87efyzl3n8.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--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).