similarity index 99%
rename from meta/recipes-support/pinentry/pinentry-1.3.0/gpg-error_pkconf.patch
rename to meta/recipes-support/pinentry/pinentry-1.3.1/gpg-error_pkconf.patch
@@ -1,4 +1,4 @@
-From ccc3c6a8d469bbfa6717b970cfe70816c1fd545e Mon Sep 17 00:00:00 2001
+From 7e830146d823ada77ae0df30c210366e2228c291 Mon Sep 17 00:00:00 2001
From: Armin Kuster <akuster@mvista.com>
Date: Fri, 2 Sep 2005 11:50:01 +0000
Subject: [PATCH] Add gtk+, avahi, dbus-0.34 (.36 coming soon) and
similarity index 97%
rename from meta/recipes-support/pinentry/pinentry-1.3.0/libassuan_pkgconf.patch
rename to meta/recipes-support/pinentry/pinentry-1.3.1/libassuan_pkgconf.patch
@@ -1,4 +1,4 @@
-From fb6179fabb5e793a83cbb0d0d45814d99b97807a Mon Sep 17 00:00:00 2001
+From f188518712071b49e29d7ed692b81340dbbb6c89 Mon Sep 17 00:00:00 2001
From: Armin Kuster <akuster@mvista.com>
Date: Thu, 22 May 2014 10:50:00 +0100
Subject: [PATCH] libassuan: Improve pkgconfig support
@@ -15,10 +15,10 @@ Signed-off-by: Armin Kuster <akuster@mvista.com>
2 files changed, 9 insertions(+), 89 deletions(-)
diff --git a/configure.ac b/configure.ac
-index f04c00d..8e6da5c 100644
+index 4944f7c..f03cbb7 100644
--- a/configure.ac
+++ b/configure.ac
-@@ -263,8 +263,8 @@ if test "$have_libassuan" = "yes"; then
+@@ -264,8 +264,8 @@ if test "$have_libassuan" = "yes"; then
[version of the libassuan library])
fi
similarity index 93%
rename from meta/recipes-support/pinentry/pinentry_1.3.0.bb
rename to meta/recipes-support/pinentry/pinentry_1.3.1.bb
@@ -16,7 +16,7 @@ SRC_URI = "${GNUPG_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
file://gpg-error_pkconf.patch \
"
-SRC_URI[sha256sum] = "9b3cd5226e7597f2fded399a3bc659923351536559e9db0826981bca316494de"
+SRC_URI[sha256sum] = "bc72ee27c7239007ab1896c3c2fae53b076e2c9bd2483dc2769a16902bce8c04"
inherit autotools pkgconfig
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *pinentry* to *1.3.1* has Succeeded. Next steps: - apply the patch: git am 0001-pinentry-upgrade-1.3.0-1.3.1.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 ef385f13a32a32ad549fd9b7b29448b41ed4c3a2 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 15 Jul 2024 19:03:57 +0000 Subject: [PATCH] pinentry: upgrade 1.3.0 -> 1.3.1 --- .../gpg-error_pkconf.patch | 2 +- .../libassuan_pkgconf.patch | 6 +++--- .../pinentry/{pinentry_1.3.0.bb => pinentry_1.3.1.bb} | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) rename meta/recipes-support/pinentry/{pinentry-1.3.0 => pinentry-1.3.1}/gpg-error_pkconf.patch (99%) rename meta/recipes-support/pinentry/{pinentry-1.3.0 => pinentry-1.3.1}/libassuan_pkgconf.patch (97%) rename meta/recipes-support/pinentry/{pinentry_1.3.0.bb => pinentry_1.3.1.bb} (93%)