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.