From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
Ralph Seichter <abbot@monksofcool.net>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] configure: fix mktemp call for macOS
Date: Sun, 16 Jun 2019 17:30:01 +0300 [thread overview]
Message-ID: <87a7ehd2mu.fsf@fifthhorseman.net> (raw)
In-Reply-To: <m2sgscgido.fsf@guru.guru-group.fi>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Fri 2019-06-14 20:57:07 +0300, Tomi Ollila wrote:
> Yes. $TMPDIR could be problematic if it makes the full (unix domain
> socket?) path be too long.
Modern, maintained version of GnuPG will only place sockets directly in
the $GNUPGHOME if /run/user/$(id -u) (i.e., $XDG_RUNTIME_DIR) is not
available.
I've just sent a message to gnupg-devel asking for help from upstream
there, this shouldn't be this complicated. see
id:87blyxd2qu.fsf@fifthhorseman.net on gnupg-devel@gnupg.org ("safe
ephemeral GnuPG homdirs").
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-06-16 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 0:26 [PATCH] configure: fix mktemp call for macOS Ralph Seichter
2019-06-14 10:57 ` David Bremner
2019-06-14 11:19 ` Ralph Seichter
2019-06-14 17:57 ` Tomi Ollila
2019-06-14 18:11 ` Tomi Ollila
2019-06-16 14:30 ` Daniel Kahn Gillmor [this message]
[not found] <CAC=HcsFwVdsxMeCLk9qZYeHbd_+qJN77EqPZ17S2UgdR0bb6mw@mail.gmail.com>
[not found] ` <5d03ff8e.1c69fb81.c82a3.d08e.GMR@mx.google.com>
2019-06-14 20:16 ` Fwd: Delivery Status Notification (Failure) Tomi Ollila
2019-06-15 17:51 ` [PATCH] configure: fix mktemp call for macOS Ralph Seichter
2019-06-16 11:12 ` Tomi Ollila
2019-06-16 15:18 ` Ralph Seichter
2019-06-17 5:10 ` 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=87a7ehd2mu.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=abbot@monksofcool.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).