From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Date: Thu, 1 Jun 2017 23:22:42 -0400 Message-ID: <20170602032242.GA19312@jasmine> References: <8737d0761f.fsf@dustycloud.org> <20170526195147.GC7831@sax.terramar.selidor.net> <20170527141146.GG1387@jasmine> <20170601084333.GQ7831@sax.terramar.selidor.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55892) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGdB6-0003gd-FT for bug-guix@gnu.org; Thu, 01 Jun 2017 23:23:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dGdB3-0004AS-8m for bug-guix@gnu.org; Thu, 01 Jun 2017 23:23:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47571) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dGdB1-00047f-0O for bug-guix@gnu.org; Thu, 01 Jun 2017 23:23:05 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dGdB0-0003bU-QW for bug-guix@gnu.org; Thu, 01 Jun 2017 23:23:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20170601084333.GQ7831@sax.terramar.selidor.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ivan Vilata i Balaguer Cc: 26610-done@debbugs.gnu.org --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 01, 2017 at 10:43:33AM +0200, Ivan Vilata i Balaguer wrote: > 0. Apply the patch. >=20 > 1. Add ``python-gpg`` at the end of ``gnu/packages/gnupg.scm`` (sorry > for my poor Scheme habilities). >=20 > 2. Run ``guix environment --ad-hoc -l gnu/packages/gnupg.scm python > assword coreutils``. >=20 > 3. Import ``gpg`` in Python and check ``gpg.version.versionstr``, dump > ``assword`` program to verify that it uses the same build of > ``python-gnupg``. >=20 > 4. Run ``assword`` and check that everything works. >=20 > Probably many steps can be done better/more easily, but my knowledge is > very limited. Links for improving that are welcome.`;)` Sounds like a good test :) > From bef8ccca58150ad4714cfa65472d5f2e9ae7b283 Mon Sep 17 00:00:00 2001 > From: Ivan Vilata-i-Balaguer > Date: Thu, 1 Jun 2017 10:33:09 +0200 > Subject: [PATCH] gnu: python-gpg: Use explicit version 1.8.0 instead of > GPGME's. >=20 > GPGME defines version 1.9.0, which isn't yet available for python-gnupg, = whose > latest version is 1.8.0, so we use that explicitly instead. Fixes #26610. >=20 > * gnu/packages/gnupg.scm (python-gpg): Use explicit version 1.8.0 instead= of GPGME's. Thank you! Pushed as 99c63f3f072e73540a65d4a7b5dac9aaeb3ed50d. --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlkw2gIACgkQJkb6MLrK fwh9xg//ZFQeO9AEaGYZICxVyNY7+63yYybHDkN3GWITYAolVWbGWHViSquzSgRG FQekivaQKd6czwJs7dBzzE6TBaKXKQTSoOoq1OKvYse/nMcFhB2Qze/0t0nEffbZ auBcgUfbrikGC9cTW0ZVC3TlFBWTQc6at8pqh68RZmddpkSRrP1afX5PYgbKpRL+ rVSTc8fQUHXxIoZeJ4SKQS3V6kj0wSpKKqGf95MVtgHOp9xHoz+svDNAJEX2IBen ObTQb7sgRLm+GyLUAIJNczTUiLz5r02LFZfT9TM1ggxKCt1qmj9oflWMpJg+8pWL Hd3fP+C1ZCs+KaH855JEy1ulKody10+lCJae1+xh+zp1DE4kd2akz1kEJEDPgTtK PzD99sp+g37Rq4XYnN5GZK4575hDS2k1oq0CoLX9UjFWBYC/UnGqD9NL9TGaQR4h cJ4E3WPyRo3KI+FJyavlvtQWNpKWYernSFsCbS6LLUhkw3GvkqUJT38nZBSJK7bd 9yrxcLtqcAhjISHGVVAHHm5khAOP633nsVuQp35SGyOENZmN7qRcfwK1aT0FjLHy iDTKYZqF/J0JlZM23cuQzOkbNBrWcV1JTuXfpGC94gu4BolaYwqaeCnbnh8EWqOT OpGNVCeeWQL5eKsHAuPT828NWOi0XdtEci0Ca/Gw/zUdO9y9dr0= =23ib -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--