From: Leo Famulari <leo@famulari.name>
To: 52483@debbugs.gnu.org
Subject: bug#52483: GnuPG 2.2.30 cannot do symmetric encryption
Date: Tue, 14 Dec 2021 11:46:12 -0500 [thread overview]
Message-ID: <YbjKVHCCHa8OvKqS@jasmine.lan> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 786 bytes --]
Our GnuPG package is version 2.2.30, which includes this bug:
https://dev.gnupg.org/T5577
The effect of this bug is that symmetric encryption / decryption does
not work. The bug was fixed in 2.2.31 and 2.3.3.
Changing GnuPG will cause 2406 rebuilds. I think that's suboptimal but
it's the situation.
There is a gnupg-2.2.32 package, but it's hidden because it would break
emacs-pinentry:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gnupg.scm?id=861ee6d908fefc47d765f81e33cdf6f84b6d50eb#n350
Here is a patch that unhides gnupg-2.2.32, updates it to 2.2.33, and
makes emacs-pinentry use that package variant.
If emacs-pinentry cannot use a current GnuPG, what should we do? And
maybe we don't need emacs-pinentry anymore?:
https://emacs.stackexchange.com/a/64721
[-- Attachment #1.2: 0001-gnu-GnuPG-Update-gnupg-2.2.32-to-2.2.33.patch --]
[-- Type: text/plain, Size: 2319 bytes --]
From b80a537cb9529b2f186519684901fe2be9e0a0f0 Mon Sep 17 00:00:00 2001
From: Leo Famulari <leo@famulari.name>
Date: Tue, 14 Dec 2021 11:40:28 -0500
Subject: [PATCH] gnu: GnuPG: Update gnupg-2.2.32 to 2.2.33.
* gnu/packages/gnupg.scm (gnupg-2.2.32): Replace with ...
(gnupg-2.2.33): ... new variable.
* gnu/packages/emacs-xyz.scm (emacs-pinentry)[propagated-inputs]: Use
gnupg-2.2.33.
---
gnu/packages/emacs-xyz.scm | 2 +-
gnu/packages/gnupg.scm | 13 +++----------
2 files changed, 4 insertions(+), 11 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 32915fb6ed..5ce07645ce 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -21238,7 +21238,7 @@ (define-public emacs-pinentry
"1lf30q6r8nz5cjzclbb9bbymsk2y75nskvb55hnjdv93gr3j0sik"))))
(build-system emacs-build-system)
(propagated-inputs
- (list gnupg))
+ (list gnupg-2.2.33))
(home-page "https://elpa.gnu.org/packages/pinentry.html")
(synopsis "GnuPG Pinentry server implementation")
(description
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 665e9e3021..fc7c1fbee0 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -347,24 +347,17 @@ (define-public gnupg
(properties '((ftp-server . "ftp.gnupg.org")
(ftp-directory . "/gcrypt/gnupg")))))
-(define-public gnupg-2.2.32
+(define-public gnupg-2.2.33
(package
(inherit gnupg)
- (version "2.2.32")
-
- ;; Hide this version because packages like 'emacs-pinentry' propagate the
- ;; default GnuPG and "guix install gnupg emacs-pinentry" would fail with a
- ;; collision error.
- (properties `((hidden? . #t)
- ,@(package-properties gnupg)))
-
+ (version "2.2.33")
(source (origin
(inherit (package-source gnupg))
(uri (string-append "mirror://gnupg/gnupg/gnupg-" version
".tar.bz2"))
(sha256
(base32
- "0506gv54z10c96z5821z9p0ksibk1pfilsmag39ffqrcz0sinmxj"))))))
+ "1qz403080hwba8j8vpnfkvh7clg1dbg74kdn1d0p0g84iip87246"))))))
(define-public gnupg-1
(package (inherit gnupg)
--
2.34.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-12-14 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 16:46 Leo Famulari [this message]
2021-12-14 17:32 ` bug#52483: GnuPG 2.2.30 cannot do symmetric encryption 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
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=YbjKVHCCHa8OvKqS@jasmine.lan \
--to=leo@famulari.name \
--cc=52483@debbugs.gnu.org \
/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).