On Thu, 14 Jun 2018 09:14, daniel.baum...@progress-linux.org said: > when locally backporting gnupg2, I noticed that 2.2.8-1 now FTBFS on > stretch due to old libgpg-error. Would you mind bumping build-depends
Please apply the attached patch to GnuPG 2.2.8 as suggested by https://dev.gnupg.org/T4012 Salam-Shalom, Werner -- # Please read: Daniel Ellsberg - The Doomsday Machine # Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
From 18274db32b5dea7fe8db67043a787578c975de4d Mon Sep 17 00:00:00 2001
From: Werner Koch <w...@gnupg.org>
Date: Fri, 8 Jun 2018 22:01:10 +0200
Subject: [PATCH GnuPG] gpg: Allow building with older libgpg-error.
* g10/mainproc.c (proc_encrypted): Use constant from logging.h
--
Because the log levels are enums I had to change there names in
libgpg-error to avoid clashes. Master uses the new names but 2.2
needs to stick to the old names.
Fixes-commit: 825909e9cd5f344ece6c0b0ea3a9475df1d643de
Signed-off-by: Werner Koch <w...@gnupg.org>
---
g10/mainproc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/g10/mainproc.c b/g10/mainproc.c
index 72b0dd828..f5cc4532a 100644
--- a/g10/mainproc.c
+++ b/g10/mainproc.c
@@ -683,7 +683,7 @@ proc_encrypted (CTX c, PACKET *pkt)
* are rare in practice we print a hint on how to decrypt
* such messages. */
log_string
- (GPGRT_LOGLVL_INFO,
+ (GPGRT_LOG_INFO,
_("Hint: If this message was created before the year 2003 it is\n"
"likely that this message is legitimate. This is because back\n"
"then integrity protection was not widely used.\n"));
--
2.11.0
pgpjcNzLcqdEE.pgp
Description: PGP signature
