From: Leo Famulari <leo@famulari.name>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Ethan Blanton <elb@kb8ojh.net>, 62294@debbugs.gnu.org
Subject: bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream
Date: Tue, 4 Apr 2023 12:23:39 -0400 [thread overview]
Message-ID: <ZCxPC6sPREuu1ipV@jasmine.lan> (raw)
In-Reply-To: <868rf8vuz4.fsf@gmail.com>
On Tue, Apr 04, 2023 at 11:48:31AM +0200, Simon Tournier wrote:
> On Mon, 20 Mar 2023 at 09:01, Ethan Blanton via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> > I believe the pin on 2.2.32 can be lifted, but as gnupg is important
> > infrastructure I am unsure about directly submitting a patch to update
> > to a newer version.
Thanks for letting us know!
> Well, graft does not seem recommended because it would update to two
> versions. And update the package would be a core-updates.
>
> Well, maybe it could be of the current core-updates dance. Could you
> send a patch for core-updates?
GnuPG does have a large number of dependent packages, but I'd argue
that's either 1) a bug or 2) something we should ignore and update
freely. It's a critical package, and did not used to have such a large
number of dependents. It's really a problem for the distro if we don't
allow ourselves to update packages like this freely.
next prev parent reply other threads:[~2023-04-04 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 13:01 bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream Ethan Blanton via Bug reports for GNU Guix
2023-04-04 9:48 ` Simon Tournier
2023-04-04 16:23 ` Leo Famulari [this message]
2023-04-04 17:31 ` Simon Tournier
2023-04-05 1:27 ` Leo Famulari
2023-04-05 6:49 ` Simon Tournier
2023-04-06 13:22 ` Ethan Blanton via Bug reports for GNU Guix
2023-05-07 15:03 ` Maxim Cournoyer
2023-04-04 16:33 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZCxPC6sPREuu1ipV@jasmine.lan \
--to=leo@famulari.name \
--cc=62294@debbugs.gnu.org \
--cc=elb@kb8ojh.net \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).