Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gnupg: adopt, update to 2.3.7.
Date: Tue, 12 Jul 2022 16:34:00 +0200	[thread overview]
Message-ID: <20220712143400.krSqBSuT1a2yE1rddHzLSvKstkvZ-kIz8h0HXbjNyd0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38021@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

gnupg: adopt, update to 2.3.7.
https://github.com/void-linux/void-packages/pull/38021

Description:
## Test/Stable/LTS/Legacy?!

GnuPG has a few different development branches, and they do change their mind sometimes about what those are. They used to say this:

> We are pleased to announce the availability of a new GnuPG release:
> version 2.3.0.  This release marks the start of public testing releases
> eventually leading to a new stable version 2.4.

Source: https://lists.gnupg.org/pipermail/gnupg-announce/2021q2/000458.html

But with 2.3.3, they changed their mind:

> Three different series of GnuPG are actively maintained:
> 
> - Version 2.3 is the current stable version with a lot of new features
>   compared to 2.2.  This announcement is about the latest release of
>   this series.
> 
> - Version 2.2 is our LTS (long term support) version and guaranteed to
>   be maintained at least until the end of 2024.
>   See https://gnupg.org/download/index.html#end-of-life
> 
> - Version 1.4 is only maintained to allow decryption of very old data
>   which is, for security reasons, not anymore possible with other GnuPG
>   versions.

Source: https://lists.gnupg.org/pipermail/gnupg-announce/2021q4/000466.html

I'd say packaging stable instead of LTS is fine, and if someone really needs LTS then we should have a separate LTS package instead.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

So, considering this is a bit of a bigger change I selected `briefly` here, but I did do quite a bit of testing on my machine, and I've not noticed any breakage yet. Encryption/decryption still works, I can still authenticate to servers via ssh, with the key residing on a yubikey being accessed through gnupg-agent, everything good.

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


  reply	other threads:[~2022-07-12 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 11:32 [PR PATCH] " jcgruenhage
2022-07-12 14:34 ` leahneukirchen [this message]
2022-07-20  6:36 ` vigoux
2022-07-20  6:46 ` vigoux
2022-07-20  7:53 ` vigoux
2022-07-20  9:42 ` jcgruenhage

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220712143400.krSqBSuT1a2yE1rddHzLSvKstkvZ-kIz8h0HXbjNyd0@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).