From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite. Date: Wed, 27 Dec 2017 19:57:17 -0500 Message-ID: <87lghnmzyq.fsf@netris.org> References: <20171220201341.6365.99040@vcs0.savannah.gnu.org> <20171220201342.95BEC2044F@vcs0.savannah.gnu.org> <87608tni72.fsf@netris.org> <20171227020406.GA15719@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUMWG-0006B0-T5 for guix-devel@gnu.org; Wed, 27 Dec 2017 19:58:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eUMWB-0000BL-Ci for guix-devel@gnu.org; Wed, 27 Dec 2017 19:58:00 -0500 Received: from world.peace.net ([50.252.239.5]:60318) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eUMWB-0008Rs-1h for guix-devel@gnu.org; Wed, 27 Dec 2017 19:57:55 -0500 In-Reply-To: <20171227020406.GA15719@jasmine.lan> (Leo Famulari's message of "Tue, 26 Dec 2017 21:04:06 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > On Tue, Dec 26, 2017 at 07:11:13PM -0500, Mark H Weaver wrote: >> > Author: Leo Famulari >> > Date: Wed Dec 20 03:20:01 2017 -0500 >> > >> > gnu: gpgme: Build with the latest GnuPG. >> > >> > * gnu/packages/gnupg.scm (gpgme)[inputs]: Use the latest gnupg package. >> > [arguments]: Keep a reference to the gnupg package used for build. >> >> Clearly you were aware that python-pygpgme needed adjustment to continue >> building, and I appreciate your attention to detail here, but something >> seems to have gone wrong. Since these commits, Hydra has failed to >> build python-pygpgme and python2-pygpgme on all hydra-supported systems: > > Thank you for bringing this to my attention. > > It's a consequence of having configured GPGME with --enable-fixed-path, > which in our case forces GPGME to use the GnuPG executable it was built > with. [0] > > I made this change rather late in the development of these patches, > after having tested them more fully. > > Since we previously let GPGME find GnuPG in the environment, and that > worked fine, I'll revert that part of the change shortly. > > [0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29781#25 Thanks for looking into it! Alas, your most recent changes seem to have now broken qgpgme: https://hydra.gnu.org/eval/109869#tabs-now-fail https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.i686-linux https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.armhf-linux Mark