From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: gnupg-2.4 breaks Emacs EasyPG
Date: Tue, 04 Jul 2023 21:07:24 +0100 [thread overview]
Message-ID: <87v8ez30c2.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
gnupg-2.4 breaks Emacs EasyPG (which does show up in test failures
too, but IIRC it hangs at runtime as well).
Upstream don't intend on applying the fix to gnupg-2.4 so distributions
will need to backport the gnupg patch (see below).
I haven't yet dug up the patch that gniibe mentions they sent to Emacs
though.
Bug: https://bugs.gentoo.org/907839
Bug: https://dev.gnupg.org/T6481
Patch: https://dev.gnupg.org/rG2f872fa68c6576724b9dabee9fb0844266f55d0d
(https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=2f872fa68c6576724b9dabee9fb0844266f55d0d)
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
reply other threads:[~2023-07-04 20:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8ez30c2.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox