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: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 62294@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream
Date: Thu, 6 Apr 2023 09:22:17 -0400	[thread overview]
Message-ID: <ZC7HiWzqXv2EJlIf@colt.lan> (raw)
In-Reply-To: <861qkyu8m5.fsf@gmail.com>

Simon Tournier wrote:
> Are you proposing to update ’gnupg’ from 2.2.32 to 2.2.33 or why not to
> 2.2.41?  And remove the graft ’gnupg/fixed’?

Personally, I think it should advance farther than 2.2.32, as there
are S/MIME bugs prior to 2.2.35 that prevent a variety of
commonly-issued S/MIME keys from being imported (see the link in the
original bug).  Selfishly, I have one of those keys and it's a problem
for me, but in general, it seems to include some keys issued by state
agencies in Europe, as well as private issuers in the US and possibly
other locations.




  reply	other threads:[~2023-04-06 13:23 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
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 [this message]
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=ZC7HiWzqXv2EJlIf@colt.lan \
    --to=bug-guix@gnu.org \
    --cc=62294@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    --cc=leo@famulari.name \
    --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).