[debbugs-tracker] bug#26610: closed (python-gpg broke; python-gpg 1.9.0 does not exist)

[GNU bug Tracking System]

Your message dated Thu, 1 Jun 2017 23:22:42 -0400
with message-id <address@hidden>
and subject line Re: bug#26610: python-gpg broke; python-gpg 1.9.0 does not 
exist
has caused the debbugs.gnu.org bug report #26610,
regarding python-gpg broke; python-gpg 1.9.0 does not exist
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26610: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26610
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> python-gpg broke; python-gpg 1.9.0 does not exist
>
>
>
>
> Date: 
>
> Sat, 22 Apr 2017 11:37:00 -0500
>
>
>
>
> User-agent: 
>
> mu4e 0.9.18; emacs 25.1.1
>
>
>
>
> Commit 8439c9c05e upgraded gpgme to 1.9.0.
>
> Unfortunately, python-gpg's version is tied to gpgme:
>
> (define-public python-gpg
>   (package
>     (name "python-gpg")
>     (version (package-version gpgme))
>     ;; [...]
>
> This is a problem, because upgrading gpgme "automatically" upgraded
> python-gpg, and there is no python-gpg release of 1.9.0.  The latest
> release is 1.8.0:
>
>   https://pypi.python.org/pypi/gpg/1.8.0
>
> I'm not sure it makes sense to tie the package version to python-gpg's
> package version anyway... if upgrading gpgme does trigger the upgrade of
> python-gpg "automatically", then that would mean that even if there was
> a pythong-gpg available with the new version, the hash would be
> incorrect.
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Date: Thu, 1 Jun 2017 23:22:42 -0400 User-agent: Mutt/1.8.2 (2017-04-18)

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 <address@hidden>
> 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.

signature.asc
Description: PGP signature

--- End Message ---