From: Leo Famulari <leo@famulari.name>
To: Ivan Vilata i Balaguer <ivan@selidor.net>
Cc: 26610-done@debbugs.gnu.org
Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist
Date: Thu, 1 Jun 2017 23:22:42 -0400 [thread overview]
Message-ID: <20170602032242.GA19312@jasmine> (raw)
In-Reply-To: <20170601084333.GQ7831@sax.terramar.selidor.net>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Thu, Jun 01, 2017 at 10:43:33AM +0200, Ivan Vilata i Balaguer wrote:
> 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.`;)`
Sounds like a good test :)
> 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.
Thank you! Pushed as 99c63f3f072e73540a65d4a7b5dac9aaeb3ed50d.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-02 3:23 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
2017-06-02 3:22 ` Leo Famulari [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170602032242.GA19312@jasmine \
--to=leo@famulari.name \
--cc=26610-done@debbugs.gnu.org \
--cc=ivan@selidor.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.