@@ -1,4 +1,4 @@
-From 581919f3af914c6b62e51b345d5d15e709f20e77 Mon Sep 17 00:00:00 2001
+From 02e885d9d3ee8fe3d7cc7a5036daa07b9af02ebb Mon Sep 17 00:00:00 2001
From: Alexander Kanavin <alex.kanavin@gmail.com>
Date: Fri, 28 Feb 2020 09:19:56 +0000
Subject: [PATCH] Do not fail when testing config scripts
@@ -14,10 +14,10 @@ Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
1 file changed, 1 deletion(-)
diff --git a/src/Makefile.am b/src/Makefile.am
-index 9389e99..6ded263 100644
+index e56bb23..8c3ba7b 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
-@@ -324,6 +324,5 @@ gpg-error-config: gpgrt-config gpg-error-config-old gpg-error-config-test.sh
+@@ -326,6 +326,5 @@ gpg-error-config: gpgrt-config gpg-error-config-old gpg-error-config-test.sh
else \
echo "no"; \
echo "*** Please report to <https://bugs.gnupg.org> with gpg-error-config-test.log"; \
@@ -1,4 +1,4 @@
-From 3529df77cd20253ce2a9c1962d7a72058a04fd98 Mon Sep 17 00:00:00 2001
+From 423cc00b6aa5eaaed53b8533376db3b4321102be Mon Sep 17 00:00:00 2001
From: Hongxu Jia <hongxu.jia@windriver.com>
Date: Wed, 21 Aug 2024 20:03:29 -0700
Subject: [PATCH] support pkgconfig
similarity index 95%
rename from meta/recipes-support/libgpg-error/libgpg-error_1.51.bb
rename to meta/recipes-support/libgpg-error/libgpg-error_1.53.bb
@@ -20,7 +20,7 @@ SRC_URI = "${GNUPG_MIRROR}/libgpg-error/libgpg-error-${PV}.tar.bz2 \
file://run-ptest \
"
-SRC_URI[sha256sum] = "be0f1b2db6b93eed55369cdf79f19f72750c8c7c39fc20b577e724545427e6b2"
+SRC_URI[sha256sum] = "6a0721b52027415f53abcbf63b5c37776a0f774d9126d560a3ce76c0eb42903f"
BINCONFIG = "${bindir}/gpg-error-config"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libgpg-error* to *1.53* has Succeeded. Next steps: - apply the patch: git am 0001-libgpg-error-upgrade-1.51-1.53.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 43f400043b6d56c7645fb7aa571cf95b6441728a Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Tue, 15 Apr 2025 13:26:05 +0000 Subject: [PATCH] libgpg-error: upgrade 1.51 -> 1.53 --- .../0001-Do-not-fail-when-testing-config-scripts.patch | 6 +++--- .../libgpg-error/libgpg-error/pkgconfig.patch | 2 +- .../{libgpg-error_1.51.bb => libgpg-error_1.53.bb} | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) rename meta/recipes-support/libgpg-error/{libgpg-error_1.51.bb => libgpg-error_1.53.bb} (95%)