From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libgpg-error: Update to version 1.47
Date: Wed, 19 Apr 2023 14:31:38 +0200 [thread overview]
Message-ID: <20230419123141.2778769-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230419123141.2778769-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3064 bytes --]
- Update from version 1.46 to 1.47
- Update of rootfile
- Changelog
Noteworthy changes in version 1.47 (2023-04-06) [C34/A34/R0]
* New error codes for PUKs and reset codes. [T6421]
* Avoid segv in logging with improper use of the "socket://".
[rE68333be630]
* Fixed translation of argparse's internal option --help.
[rE885a287a57]
* Interface changes relative to the 1.46 release:
GPG_ERR_SOURCE_TKD NEW.
GPG_ERR_BAD_PUK NEW.
GPG_ERR_NO_RESET_CODE NEW.
GPG_ERR_BAD_RESET_CODE NEW.
GPGRT_SPAWN_KEEP_STDIN NEW.
GPGRT_SPAWN_KEEP_STDOUT NEW.
GPGRT_SPAWN_KEEP_STDERR NEW.
GPGRT_SPAWN_INHERIT_FILE NEW.
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
config/rootfiles/common/libgpg-error | 3 ++-
lfs/libgpg-error | 6 +++---
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/config/rootfiles/common/libgpg-error b/config/rootfiles/common/libgpg-error
index 77a12be29..08079ed9c 100644
--- a/config/rootfiles/common/libgpg-error
+++ b/config/rootfiles/common/libgpg-error
@@ -6,7 +6,7 @@ usr/bin/gpg-error
#usr/lib/libgpg-error.la
#usr/lib/libgpg-error.so
usr/lib/libgpg-error.so.0
-usr/lib/libgpg-error.so.0.33.1
+usr/lib/libgpg-error.so.0.34.0
#usr/lib/pkgconfig/gpg-error.pc
#usr/share/aclocal/gpg-error.m4
#usr/share/aclocal/gpgrt.m4
@@ -41,3 +41,4 @@ usr/lib/libgpg-error.so.0.33.1
#usr/share/locale/vi/LC_MESSAGES/libgpg-error.mo
#usr/share/locale/zh_CN/LC_MESSAGES/libgpg-error.mo
#usr/share/locale/zh_TW/LC_MESSAGES/libgpg-error.mo
+#usr/share/man/man1/gpgrt-config.1
diff --git a/lfs/libgpg-error b/lfs/libgpg-error
index fa7b63f42..f60f1ae82 100644
--- a/lfs/libgpg-error
+++ b/lfs/libgpg-error
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 1.46
+VER = 1.47
THISAPP = libgpg-error-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 6748c463256b7d0a05fe89a63c5f3abda1975d861c35821248664f2f09cd2273ef619d12408b6107a99519939ca7214f492e705c29f52f7bbdc422237281c1ca
+$(DL_FILE)_BLAKE2 = bc04efa0686b1b7d7cdce045fc080c090c1abec60349b673c2e1ce27900483aea090eb6ebcb3fb49a4eed36f18156a12413d5446f739475632f4ed2a2481ff27
install : $(TARGET)
--
2.40.0
next prev parent reply other threads:[~2023-04-19 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 12:31 [PATCH] libgcrypt: Update to version 1.10.2 Adolf Belka
2023-04-19 12:31 ` Adolf Belka [this message]
2023-04-19 12:31 ` [PATCH] parted: Update to version 3.6 Adolf Belka
2023-04-19 12:31 ` [PATCH] samba: Update to version 4.18.1 Adolf Belka
2023-04-19 12:31 ` [PATCH] sdl2: Update to version 2.26.5 Adolf Belka
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=20230419123141.2778769-2-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox