GNU bug report logs - #26610
python-gpg broke; python-gpg 1.9.0 does not exist

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Christopher Allan Webber <cwebber <at> dustycloud.org>
Subject: bug#26610: closed (Re: bug#26610: python-gpg broke; python-gpg
 1.9.0 does not exist)
Date: Fri, 02 Jun 2017 03:23:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#26610: python-gpg broke; python-gpg 1.9.0 does not exist

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 26610 <at> debbugs.gnu.org.

-- 
26610: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26610
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Leo Famulari <leo <at> famulari.name>
To: Ivan Vilata i Balaguer <ivan <at> selidor.net>
Cc: 26610-done <at> debbugs.gnu.org
Subject: Re: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist
Date: Thu, 1 Jun 2017 23:22:42 -0400

[Message part 3 (text/plain, inline)]

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 <at> 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.

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Christopher Allan Webber <cwebber <at> dustycloud.org>
To: "'bug-guix\@gnu.org'" <bug-guix <at> gnu.org>, Leo Famulari <leo <at> famulari.name>
Subject: python-gpg broke; python-gpg 1.9.0 does not exist
Date: Sat, 22 Apr 2017 11:37:00 -0500

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.