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 51A826DE1536 for ; Tue, 14 Feb 2017 14:14:24 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[AWL=0.000, HEADER_FROM_DIFFERENT_DOMAINS=0.001] 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 CIB4peBReW9x for ; Tue, 14 Feb 2017 14:14:23 -0800 (PST) X-Greylist: delayed 1874 seconds by postgrey-1.35 at arlo; Tue, 14 Feb 2017 14:14:23 PST Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 77F3B6DE1512 for ; Tue, 14 Feb 2017 14:14:23 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cdkrm-0006uM-57; Tue, 14 Feb 2017 16:42:30 -0500 Received: (nullmailer pid 9781 invoked by uid 1000); Tue, 14 Feb 2017 21:43:00 -0000 From: David Bremner To: notmuch@notmuchmail.org Cc: aidecode@aidecode.name Subject: Proposed fix for test failures due to long socket paths Date: Tue, 14 Feb 2017 16:42:37 -0500 Message-Id: <20170214214239.9330-1-david@tethera.net> X-Mailer: git-send-email 2.11.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: Tue, 14 Feb 2017 22:14:24 -0000 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.