[git] GnuPG - branch, STABLE-BRANCH-2-2, updated. gnupg-2.2.8-2-g18274db

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GNU Privacy Guard".

The branch, STABLE-BRANCH-2-2 has been updated
       via  18274db32b5dea7fe8db67043a787578c975de4d (commit)
      from  e9667dd20a3a71c0a51d20ac4b1aa758e5bb5ada (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 18274db32b5dea7fe8db67043a787578c975de4d
Author: Werner Koch <[email protected]>
Date:   Fri Jun 8 22:01:10 2018 +0200

    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 <[email protected]>

diff --git a/g10/mainproc.c b/g10/mainproc.c
index 72b0dd8..f5cc453 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"));

-----------------------------------------------------------------------

Summary of changes:
 g10/mainproc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
The GNU Privacy Guard
http://git.gnupg.org