GNU bug report logs -
#29792
[PATCH] gnu: gnupg@2.0: Superseded by the latest GnuPG.
Previous Next
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
Leo Famulari <leo <at> 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’.
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.