From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Date: Sat, 22 Apr 2017 11:37:00 -0500 Message-ID: <8737d0761f.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1y2v-0003BF-8S for bug-guix@gnu.org; Sat, 22 Apr 2017 12:38:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1y2s-0003kF-4U for bug-guix@gnu.org; Sat, 22 Apr 2017 12:38:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:36422) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d1y2s-0003kB-1E for bug-guix@gnu.org; Sat, 22 Apr 2017 12:38:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d1y2r-0008Mf-RQ for bug-guix@gnu.org; Sat, 22 Apr 2017 12:38:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1y1z-000330-L3 for bug-guix@gnu.org; Sat, 22 Apr 2017 12:37:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1y1w-0003Ry-F3 for bug-guix@gnu.org; Sat, 22 Apr 2017 12:37:07 -0400 Received: from dustycloud.org ([50.116.34.160]:48874) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d1y1w-0003Rl-Al for bug-guix@gnu.org; Sat, 22 Apr 2017 12:37:04 -0400 List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 26610@debbugs.gnu.org, leo@famulari.name 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.