From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 52483-done@debbugs.gnu.org
Subject: bug#52483: GnuPG 2.2.30 cannot do symmetric encryption
Date: Sun, 26 Dec 2021 17:46:41 -0500 [thread overview]
Message-ID: <Ycjw0XsEQZEwC06M@jasmine.lan> (raw)
In-Reply-To: <Yb+XyR/XFKpKLr0s@jasmine.lan>
On Sun, Dec 19, 2021 at 03:36:25PM -0500, Leo Famulari wrote:
> On Sun, Dec 19, 2021 at 03:25:42PM -0500, Maxim Cournoyer wrote:
> > > I tested with GnuPG 2.2.23 by building all packages that depend directly
> > > on GnuPG. There were no new failures on x86_64-linux when using GnuPG
> > > 2.2.32.
>
> I see that my message was confusing, with mixed up version numbers.
> There's no regressions on x86_64 with 2.2.32. Since it fixes this bug,
> I'd like to make it available soon. Maybe we can unhide the gnupg-2.2.32
> variable, and remove emacs-pinentry, since everyone is saying that it's
> no longer useful.
I pushed commit d03aa942d, which makes GnuPG 2.2.32 available in the UI.
I didn't remove emacs-pinentry... that's something that Emacs users
should decide how to handle.
next prev parent reply other threads:[~2021-12-26 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 16:46 bug#52483: GnuPG 2.2.30 cannot do symmetric encryption Leo Famulari
2021-12-14 17:32 ` Leo Famulari
2021-12-14 17:33 ` bug#52483: [PATCH v2] gnu: GnuPG: Update gnupg-2.2.32 to 2.2.33 Leo Famulari
2021-12-17 17:32 ` Leo Famulari
2021-12-18 4:56 ` bug#52483: GnuPG 2.2.30 cannot do symmetric encryption Maxim Cournoyer
2021-12-18 23:53 ` Leo Famulari
2021-12-19 20:25 ` Maxim Cournoyer
2021-12-19 20:33 ` Leo Famulari
2021-12-19 20:36 ` Leo Famulari
2021-12-23 0:01 ` Leo Famulari
2021-12-26 22:46 ` Leo Famulari [this message]
2021-12-19 1:32 ` Michael Rohleder
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=Ycjw0XsEQZEwC06M@jasmine.lan \
--to=leo@famulari.name \
--cc=52483-done@debbugs.gnu.org \
--cc=maxim.cournoyer@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).