From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 52483@debbugs.gnu.org
Subject: bug#52483: GnuPG 2.2.30 cannot do symmetric encryption
Date: Sun, 19 Dec 2021 15:25:42 -0500 [thread overview]
Message-ID: <874k744a0p.fsf@gmail.com> (raw)
In-Reply-To: <Yb50XTFDq95dwz4s@jasmine.lan> (Leo Famulari's message of "Sat, 18 Dec 2021 18:53:01 -0500")
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> On Fri, Dec 17, 2021 at 11:56:41PM -0500, Maxim Cournoyer wrote:
>> I'm testing this:
>>
>> --8<---------------cut here---------------start------------->8---
>> gnu: gnupg: Update to 2.3.3.
>>
>> * gnu/packages/gnupg.scm (gnupg): Update to 2.3.3.
>> (gnupg-2.2.32): Delete variable.
>> (qgpgme)[native-inputs]: Use the regular gnupg package.
>
> Okay. Make sure to also adjust emacs-pinentry.
>
> 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 ended up sticking with 2.2.33, since this is the current "LTS"
release. Unfortunately it fails 3 new tests of python-gnupg, and its
author think it is a regression in GnuPG itself [0].
[0] https://github.com/vsajip/python-gnupg/issues/163
We'll see what upstream has to say about it.
Thank you,
Maxim
next prev parent reply other threads:[~2021-12-19 20:26 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 [this message]
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
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=874k744a0p.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=52483@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).