From: Tomi Ollila <domo141@gmail.com>
To: notmuch@notmuchmail.org
Subject: Fwd: Delivery Status Notification (Failure)
Date: Fri, 14 Jun 2019 23:16:30 +0300 [thread overview]
Message-ID: <CAC=HcsGK4CynT5_LQ6ezqMFFuv2u5kdfk4=5a-J0A5S-mcxoqQ@mail.gmail.com> (raw)
In-Reply-To: <5d03ff8e.1c69fb81.c82a3.d08e.GMR@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 2246 bytes --]
Sorry for the mess -- too tired to fight with this -- hopefully the content
is readable below (will not know before mail leaves...)
[image: Virhekuvake]
Viestiä ei toimitettu
Olet lähettämässä viestiä toisesta osoitteesta tai aliaksesta
Lähetysosoite-ominaisuudella. Lähetysosoite-tilin asetukset ovat
virheelliset tai vanhentuneet. Tarkista kyseisen tilin asetukset ja yritä
lähettää viesti uudelleen.
LISÄTIETOJA <https://support.google.com/mail/?p=CustomFromDenied>
---------- Forwarded message ----------
From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Cc:
Bcc:
Date: Fri, 14 Jun 2019 23:11:47 +0300
Subject: Re: [PATCH] configure: fix mktemp call for macOS
Hi
cannot (easily) attach to the thread from this account, therefore...
First, it would be better if
TEMP_GPG=$(mktemp -d "${TMPDIR:-/tmp}/notmuch.XXXXXX")
worked, then the behaviour on Linux would not change.
To me it looks like the problem in that one debian bug (i847206) is that the
directory pathname is already like 106 octets -- and on Linux the maximun
unix domain socket pathname is 108 octets -- gpg socket is probably longer
than 1 octet here :D
In case of macOS (and BSD, so says internet) max pathname is 104 octets
In Ralph's example $TMPDIR is
/var/folders/m_/w5lk3r_1495dhnl4l0s96pr00000gn/T/
-- 50 octets. Also probably older system would not have so much longer
tmpdir settings that appending gpg socket name would make length pass
104 octets...
But I am not personally against "hardcoding" /tmp/ (i.e. ignoring TMPDIR) as
prefix location where temporary directory for GNUPGHOME is created
(and, again I don't see where it could fail (barring cases similar to xkcd
workflow)), but perhaps the behavioural change could be mentioned in
the commit message.
(BTW: in case of clutter, by default $TMPDIR is not set, and if set then
user is
responsible of cleaning the clutter. if macOS does its own magic with
$TMPDIR (i.e. w/o user's intervention) then os should also take care
of the clutter...)
(BTW2: I was about to claim that ./configure in notmuch removes GNUPGHOME
quickly after its use has ended, but I did not look anything doing that...)
Tomi
[-- Attachment #1.2: Type: text/html, Size: 3811 bytes --]
[-- Attachment #2: icon.png --]
[-- Type: image/png, Size: 5747 bytes --]
next parent reply other threads:[~2019-06-14 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC=HcsFwVdsxMeCLk9qZYeHbd_+qJN77EqPZ17S2UgdR0bb6mw@mail.gmail.com>
[not found] ` <5d03ff8e.1c69fb81.c82a3.d08e.GMR@mx.google.com>
2019-06-14 20:16 ` Tomi Ollila [this message]
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='CAC=HcsGK4CynT5_LQ6ezqMFFuv2u5kdfk4=5a-J0A5S-mcxoqQ@mail.gmail.com' \
--to=domo141@gmail.com \
--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).