From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ivan Vilata i Balaguer Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Date: Thu, 1 Jun 2017 10:43:33 +0200 Message-ID: <20170601084333.GQ7831@sax.terramar.selidor.net> References: <8737d0761f.fsf@dustycloud.org> <20170526195147.GC7831@sax.terramar.selidor.net> <20170527141146.GG1387@jasmine> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ftEhullJWpWg/VHq" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGLiA-000877-DB for bug-guix@gnu.org; Thu, 01 Jun 2017 04:44:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dGLi6-0008FF-DC for bug-guix@gnu.org; Thu, 01 Jun 2017 04:44:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:45741) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dGLi6-0008Ef-9J for bug-guix@gnu.org; Thu, 01 Jun 2017 04:44:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dGLi5-0002BW-PB for bug-guix@gnu.org; Thu, 01 Jun 2017 04:44:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20170527141146.GG1387@jasmine> 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: Leo Famulari Cc: 26610@debbugs.gnu.org, Ivan Vilata i Balaguer --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Leo Famulari (2017-05-27 10:11:46 -0400) wrote: > You can try changing the python-gpg package's version to the last > available upstream version. On PyPi, that's 1.8.0. > > Then, try rebuilding the packages that depend on python-gpg (`guix > refresh -l python-gpg python2-gpg`). > > Hopefully it all works. Then, you can send a patch with your fix :) > > Let us know if you need help! Ok, attaching the patch. These are the steps I followed to test it: 0. Apply the patch. 1. Add ``python-gpg`` at the end of ``gnu/packages/gnupg.scm`` (sorry for my poor Scheme habilities). 2. Run ``guix environment --ad-hoc -l gnu/packages/gnupg.scm python assword coreutils``. 3. Import ``gpg`` in Python and check ``gpg.version.versionstr``, dump ``assword`` program to verify that it uses the same build of ``python-gnupg``. 4. Run ``assword`` and check that everything works. Probably many steps can be done better/more easily, but my knowledge is very limited. Links for improving that are welcome.`;)` Thanks and cheers, -- Ivan Vilata i Balaguer -- https://elvil.net/ --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="0001-gnu-python-gpg-Use-explicit-version-1.8.0-instead-of.patch" >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. 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. * gnu/packages/gnupg.scm (python-gpg): Use explicit version 1.8.0 instead of GPGME's. --- gnu/packages/gnupg.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm index 440e7d550..c2b02789b 100644 --- a/gnu/packages/gnupg.scm +++ b/gnu/packages/gnupg.scm @@ -410,7 +410,7 @@ and every application benefits from this.") (define-public python-gpg (package (name "python-gpg") - (version (package-version gpgme)) + (version "1.8.0") (source (origin (method url-fetch) (uri (pypi-uri "gpg" version)) -- 2.12.2 --ftEhullJWpWg/VHq--