From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: Leo Famulari <leo@famulari.name>
Cc: 26610@debbugs.gnu.org, Ivan Vilata i Balaguer <ivan@selidor.net>
Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist
Date: Thu, 1 Jun 2017 10:43:33 +0200 [thread overview]
Message-ID: <20170601084333.GQ7831@sax.terramar.selidor.net> (raw)
In-Reply-To: <20170527141146.GG1387@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
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/
[-- Attachment #2: 0001-gnu-python-gpg-Use-explicit-version-1.8.0-instead-of.patch --]
[-- Type: text/plain, Size: 1019 bytes --]
From bef8ccca58150ad4714cfa65472d5f2e9ae7b283 Mon Sep 17 00:00:00 2001
From: Ivan Vilata-i-Balaguer <ivan@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
next prev parent reply other threads:[~2017-06-01 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 16:37 bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Christopher Allan Webber
2017-04-22 22:43 ` Leo Famulari
2017-05-26 19:51 ` Ivan Vilata i Balaguer
2017-05-27 14:11 ` Leo Famulari
2017-06-01 8:43 ` Ivan Vilata i Balaguer [this message]
2017-06-02 3:22 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170601084333.GQ7831@sax.terramar.selidor.net \
--to=ivan@selidor.net \
--cc=26610@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).