From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 085096DE173D for ; Wed, 15 Feb 2017 10:17:56 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.06 X-Spam-Level: X-Spam-Status: No, score=-0.06 tagged_above=-999 required=5 tests=[AWL=-0.060] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9sV9ctzigD2 for ; Wed, 15 Feb 2017 10:17:55 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTP id D56666DE173F for ; Wed, 15 Feb 2017 10:17:54 -0800 (PST) Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 7E446F98C; Wed, 15 Feb 2017 13:17:54 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 5F57A20307; Wed, 15 Feb 2017 13:17:50 -0500 (EST) From: Daniel Kahn Gillmor To: David Bremner , notmuch@notmuchmail.org Subject: Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available In-Reply-To: <20170214214239.9330-3-david@tethera.net> References: <20170214214239.9330-1-david@tethera.net> <20170214214239.9330-3-david@tethera.net> Date: Wed, 15 Feb 2017 13:17:47 -0500 Message-ID: <87efyzl3n8.fsf@alice.fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2017 18:17:56 -0000 --=-=-= Content-Type: text/plain 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOCdgUepHf6PklTkyFJitxsGSMjcFAlikm0sACgkQFJitxsGS MjfOChAAjLGntWZFomJ5QQnEpIgbszReGt8Axjg60IE2mMtY5mVxmqyLynVf4GUQ 090WuI/focGTRhsAC9LQ7UJY8TS0BafuvMAtrL8bB0oF5COIqW0djaVMEa2kNKEq ZPy4yMFRdikVggQAOjmgYGB4IXpWYoOc9u9xt6sCmLT2Y75aO3cySmN/e55uADnc C1o2uQouNkZkGWfaPbXsyjx2tIZqv0Chp1E8neKim3+9EVTTK5WRhitxOk4RxFI/ VunewFbQuibd/Gjeq83As9peNMQsyQuTsWRiPZTq6y1/8ldjBCpPxL3SVv3RtF41 UMXPo3xs9i9bulIXRGWR335w5g4Tp89RTa1vYGio0ctEnZPzkr8YBiAXsrIEMshp Km1anGeGo+/VqlGboKJAFnElcGgtH/OI8We25GC3haOkoSE/QHAbjgGYN7uoKCpb Xvz1lceygaqa9wR5ju943IPZGP4VQ2tyaboVQxe0jqZgZmDpDQZEK3zX625IcEdp DU6cnEt74xf0nn6T375nE4cG1fxh+R0FTSYMJ6jI7IWXxsTb6RqS/J5A2em7rSWV G3u1M3PdvaGGBeTxl9PEdCL4muznkufsZp/g2YViZiFuvYE2cR6yJL2ZDKpI54mN wUCMhbgfRCLtmVryNndA3IdOp7hH+CabxsLkWgRsYHIIRBlJRVE= =98J9 -----END PGP SIGNATURE----- --=-=-=--