GNU bug report logs - #29792
[PATCH] gnu: gnupg@2.0: Superseded by the latest GnuPG.

Previous Next

Package: guix-patches;

Reported by: Leo Famulari <leo <at> famulari.name>

Date: Wed, 20 Dec 2017 21:51:01 UTC

Severity: normal

Tags: patch

Done: Leo Famulari <leo <at> famulari.name>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Leo Famulari <leo <at> famulari.name>
Subject: bug#29792: closed (Re: [bug#29792] [PATCH] gnu: gnupg <at> 2.0:
 Superseded by the latest GnuPG.)
Date: Thu, 21 Dec 2017 17:46:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#29792: [PATCH] gnu: gnupg <at> 2.0: Superseded by the latest GnuPG.

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

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

-- 
29792: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29792
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: Ludovic Courtès <ludo <at> gnu.org>
Cc: 29792-done <at> debbugs.gnu.org
Subject: Re: [bug#29792] [PATCH] gnu: gnupg <at> 2.0: Superseded by the latest
 GnuPG.
Date: Thu, 21 Dec 2017 12:45:07 -0500
[Message part 3 (text/plain, inline)]
On Thu, Dec 21, 2017 at 11:11:56AM +0100, Ludovic Courtès wrote:
> Since this makes it impossible to install gnupg-2.0 unless one uses -e,
> I thought we could remove the definition altogether, but maybe what you
> propose is a good middle-ground since it gives an escape hatch for
> someone “who knows what they’re doing.”

It seems there are some big differences between 2.0 and later series.
Notably, 2.0 still uses the old pubring.gpg and secring.gpg keyrings and
supports PGP-2 keys. But 2.0 uses the newer multi-process architecture
compared to 1.4.

https://gnupg.org/faq/whats-new-in-2.1.html

So, there could be people still wanting to use 2.0 for a while. I think
we should remove it completely soonish.

I pushed as 806e891e85aff27ea87c4e60930d8c4ed7d5091f.
[signature.asc (application/pgp-signature, inline)]
[Message part 5 (message/rfc822, inline)]
From: Leo Famulari <leo <at> famulari.name>
To: guix-patches <at> gnu.org
Subject: [PATCH] gnu: gnupg <at> 2.0: Superseded by the latest GnuPG.
Date: Wed, 20 Dec 2017 16:50:11 -0500
The 2.0 series of GnuPG will stop receiving upstream support on
2017-12-31. From the release announcement of GnuPG 2.2.0:

"This release marks the start of a new long term support series
to replace the 2.0.x series which will reach end-of-life on 2017-12-31."

https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000413.html

* gnu/packages/gnupg.scm (gnupg-2.0)[properties]: New field.
---
 gnu/packages/gnupg.scm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 7a791aecd..247e907b1 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -341,7 +341,8 @@ libskba (working with X.509 certificates and CMS data).")
                 ;; Keep the old name around to ease transition.
                 (symlink "gpgv" "gpgv2")
                 (symlink "gpg" "gpg2")
-                #t)))))))))
+                #t)))))))
+   (properties `((superseded . ,gnupg)))))
 
 (define-public gnupg-1
   (package (inherit gnupg)
-- 
2.15.1




This bug report was last modified 7 years and 214 days ago.

Previous Next


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