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/
>From bef8ccca58150ad4714cfa65472d5f2e9ae7b283 Mon Sep 17 00:00:00 2001 From: Ivan Vilata-i-Balaguer <i...@selidor.net> 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