From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite. Date: Tue, 26 Dec 2017 21:04:06 -0500 Message-ID: <20171227020406.GA15719@jasmine.lan> References: <20171220201341.6365.99040@vcs0.savannah.gnu.org> <20171220201342.95BEC2044F@vcs0.savannah.gnu.org> <87608tni72.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41519) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eU14r-0007wX-Gs for guix-devel@gnu.org; Tue, 26 Dec 2017 21:04:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eU14n-0004QN-83 for guix-devel@gnu.org; Tue, 26 Dec 2017 21:04:17 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:48475) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eU14m-0004P0-Ul for guix-devel@gnu.org; Tue, 26 Dec 2017 21:04:13 -0500 Content-Disposition: inline In-Reply-To: <87608tni72.fsf@netris.org> 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: Mark H Weaver Cc: guix-devel@gnu.org --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 > >=20 > > gnu: gpgme: Build with the latest GnuPG. > > =20 > > * gnu/packages/gnupg.scm (gpgme)[inputs]: Use the latest gnupg pack= age. > > [arguments]: Keep a reference to the gnupg package used for build. >=20 > 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=3D29781#25 --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlpC/5IACgkQJkb6MLrK fwgbVw/+MX6ZT7a4+fWTYMyvGPMSts9AI2wJUwi41MZl0GQpihwzB3OD0GhOtDYI R0EfyYhlZ5D2WJiQoI5uGYF4Jpf29Ou5Jj9fcUzIquhJUFrSUkoMZql6ByolxLHq CqcaWqOIbTq6JfYLMeFqDdswf8d7SjCYn1Jm9aRmMCwnPpMcIJaceVgu5pU4UsRI 06BjtQ0vUjfHkgBuxDliqauvEtIDKGqW6DU1gIKPLg9avVJjT/J6U10MRO0wLrBZ WrnB0sFGa+aZK2+qkQSYZoypO/t5cVZh/u2xLdeuFJ9OEQn+qr+P9cTgPm07bknl zxxRluI9Gt6Y8mboob4Do+UW4ptDxR88Yn6KtYu3qJUdqi4qRPfN7O+kcSdRBlcb S1Ct59pRsMU9O8WOBHKbPykpyL0DzDTCbtdbDw0QFDPlMyOzRBkacaxRBpDZMBeU rACMZHZb2b/BfX2fq3sCACdmxSCoAcRrv1wD9bDvOo2COXyALPGIKulQ4MAbet5v bV4xaF5gP62xrgMi9asQ+/dDOYAa5+qgqrtG9XEl4F+4w+1KVcThZ/lqIvnUAKV2 1FNaqLpwM5IoBHvp7UM93XGtx6b3sup/kRK269FX3730ElzDn5eFRdRfT6Haoe8A zORNH89l6fGEIg1zi9zcOpntr+0H+Rqkd7FQWMzD2Q31bhC/B90= =6+wH -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--