unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ethan Blanton via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 62294@debbugs.gnu.org
Subject: bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream
Date: Mon, 20 Mar 2023 09:01:33 -0400	[thread overview]
Message-ID: <ZBhZLZwNF5DVW1K1@colt.lan> (raw)

It looks like the gnupg package is pinned at 2.2.32 with the following
note:

    ;; Note2: 2.2.33 currently suffers from regressions, so do not update to it
    ;; (see: https://dev.gnupg.org/T5742).

However, the bug referenced here is fixed in upstream commit
4cc724639c012215f59648cbb4b7631b9d352e36, which shipped in gnupg
2.2.34.  Meanwhile, all gnupg releases older than 2.2.35 suffer from
an S/MIME key-parsing bug (referenced in
https://www.mail-archive.com/gnupg-users@gnupg.org/msg40758.html).

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.

Ethan




             reply	other threads:[~2023-03-20 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 13:01 Ethan Blanton via Bug reports for GNU Guix [this message]
2023-04-04  9:48 ` bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream Simon Tournier
2023-04-04 16:23   ` Leo Famulari
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=ZBhZLZwNF5DVW1K1@colt.lan \
    --to=bug-guix@gnu.org \
    --cc=62294@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    /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).