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

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

[Leo Famulari]

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

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

[Ludovic Courtès]

Leo Famulari <leo@famulari.name> skribis:

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

LGTM!

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

Thanks,
Ludo’.

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

[Leo Famulari]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]