[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#29792: closed ([PATCH] gnu: address@hidden: Supers

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#29792: closed ([PATCH] gnu: address@hidden: Superseded by the latest GnuPG.)
Date: Thu, 21 Dec 2017 17:46:01 +0000

Your message dated Thu, 21 Dec 2017 12:45:07 -0500
with message-id <address@hidden>
and subject line Re: [bug#29792] [PATCH] gnu: address@hidden: Superseded by the 
latest GnuPG.
has caused the debbugs.gnu.org bug report #29792,
regarding [PATCH] gnu: address@hidden: Superseded by the latest GnuPG.
to be marked as done.

(If you believe you have received this mail in error, please contact

29792: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29792
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] gnu: address@hidden: 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."


* 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)

--- End Message ---
--- Begin Message --- Subject: Re: [bug#29792] [PATCH] gnu: address@hidden: Superseded by the latest GnuPG. Date: Thu, 21 Dec 2017 12:45:07 -0500 User-agent: Mutt/1.9.2 (2017-12-15)
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.


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.

Attachment: signature.asc
Description: PGP signature

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]