From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#26610: python-gpg broke; python-gpg 1.9.0 does not exist Date: Sat, 22 Apr 2017 18:43:07 -0400 Message-ID: <20170422224307.GA6373@jasmine> References: <8737d0761f.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54881) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d23l9-0002om-HS for bug-guix@gnu.org; Sat, 22 Apr 2017 18:44:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d23l5-0000kM-H7 for bug-guix@gnu.org; Sat, 22 Apr 2017 18:44:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:36641) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d23l4-0000k1-ML for bug-guix@gnu.org; Sat, 22 Apr 2017 18:44:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d23l4-0006xJ-Aj for bug-guix@gnu.org; Sat, 22 Apr 2017 18:44:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8737d0761f.fsf@dustycloud.org> 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 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 22, 2017 at 11:37:00AM -0500, Christopher Allan Webber wrote: > Commit 8439c9c05e upgraded gpgme to 1.9.0. >=20 > Unfortunately, python-gpg's version is tied to gpgme: >=20 > (define-public python-gpg > (package > (name "python-gpg") > (version (package-version gpgme)) > ;; [...] >=20 > 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: >=20 > https://pypi.python.org/pypi/gpg/1.8.0 I'd hoped the GPGME maintainers would release new versions of python-gpg in tandem with GPGME, but since that's not the case, we should not use gpgme's package-version in python-gpg. Can you try it? I'm not an assword user, so I can't adequately test the combination of gpgme-1.9.0 and python-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. Right, this technique doesn't work if one forgets to update the other packages... as I forgot to do in this case :) --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlj73HsACgkQJkb6MLrK fwiPXQ//eK2uiGfNAxs9Rw2B5IkzhnS9PATEg/LoURQ0yjIrsT8zj0Q92WJwsLr9 kNe1jAMovKccMDRRZSJCvzsthv1qbmz60Nzm9sSlVEFI7heXLPAzVCA+zHxsB7SY kOBL+CD+K7g7ewVMXVXh9TDwE1ankp2F7f2tJF55Mj1W+CfX3bWU2LxhuuM6n3JB 5ZH8C/9NMUb6k0z4W2zvqrfMYgcKCuuL4plAJUjSpKI0xnVtGgiVqua25nf7PGA7 lS453Q9CCRmTFbKGcbWDmpamtTk/SRkg9PwSkK4qVQeIs6s2YykVLD41Hm+Yzx0T fVvExxRPwMnG49acNQB/liSwFaSTqhG80zNGOyaC5eokBfVNu2aT0gruXClxUMzR x62YXy2WWyMgxuHlRHkfTWn88he3wLtlAFYuY5SQgZ6F3SPSXqs77w0IgZrNXn0Q ImNkfMrQJLOwubHOKLUHTRp483RSKepsTkXnTMo7/khuOkhxkIax98hLw+8974Ei cBrBFFMvw/k8ZnzpTPd6jbAKnPcODe+ZE6f2xXHdVs7XkcQmbYqhrBF/bFgTDKcH iHbIVMbdqn5glJv5XDx+o4RTOroCTpBtvvlzL9FOnV+kV4czZay4KCtwBUzRRYL5 1HU3XUki6VRNWpjQOYMPw9kFr9ncXJalAazv6xwDRWO/toKyvgo= =UKgV -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--