| Message ID | 010101a09e6e9c23-0beecf16-cab6-4076-84d3-72264e79523f-000000@us-west-2.amazonses.com |
|---|---|
| State | New |
| Headers | show |
| Series | [AUH] libtirpc: upgrading to 1.3.8 SUCCEEDED | expand |
diff --git a/meta/recipes-extended/libtirpc/libtirpc/0001-libtirpc-fix-bindresvport-build-with-clang-22-C23.patch b/meta/recipes-extended/libtirpc/libtirpc/0001-libtirpc-fix-bindresvport-build-with-clang-22-C23.patch index 4e5844e18e..1d2a9bf287 100644 --- a/meta/recipes-extended/libtirpc/libtirpc/0001-libtirpc-fix-bindresvport-build-with-clang-22-C23.patch +++ b/meta/recipes-extended/libtirpc/libtirpc/0001-libtirpc-fix-bindresvport-build-with-clang-22-C23.patch @@ -1,4 +1,4 @@ -From 0ae4371ee63e25a48777a83c0601c85c5747cbac Mon Sep 17 00:00:00 2001 +From 801ec3f723fcf6d531cb57c9f3c6ec1c51b5eb54 Mon Sep 17 00:00:00 2001 From: Khem Raj <khem.raj@oss.qualcomm.com> Date: Tue, 31 Mar 2026 23:07:09 -0700 Subject: [PATCH] libtirpc: fix bindresvport build with clang-22/C23 diff --git a/meta/recipes-extended/libtirpc/libtirpc_1.3.7.bb b/meta/recipes-extended/libtirpc/libtirpc_1.3.8.bb similarity index 93% rename from meta/recipes-extended/libtirpc/libtirpc_1.3.7.bb rename to meta/recipes-extended/libtirpc/libtirpc_1.3.8.bb index cef541e3d0..6d95f3f69d 100644 --- a/meta/recipes-extended/libtirpc/libtirpc_1.3.7.bb +++ b/meta/recipes-extended/libtirpc/libtirpc_1.3.8.bb @@ -14,7 +14,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BP}.tar.bz2 \ " UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/libtirpc/files/libtirpc/" UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)/" -SRC_URI[sha256sum] = "b47d3ac19d3549e54a05d0019a6c400674da716123858cfdb6d3bdd70a66c702" +SRC_URI[sha256sum] = "8839959bfcc7a0f4c609d8e4f53f1c67ae33de23775ec35beb39ff15adf11920" inherit autotools pkgconfig
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libtirpc* to *1.3.8* has Succeeded. Next steps: - apply the patch: git am 0001-libtirpc-upgrade-1.3.7-1.3.8.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 6c1b07a9b43aa5f61e1bc78bb1c22763c3401ae2 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 14 Sep 2026 05:29:50 +0000 Subject: [PATCH] libtirpc: upgrade 1.3.7 -> 1.3.8 --- ...0001-libtirpc-fix-bindresvport-build-with-clang-22-C23.patch | 2 +- .../libtirpc/{libtirpc_1.3.7.bb => libtirpc_1.3.8.bb} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/libtirpc/{libtirpc_1.3.7.bb => libtirpc_1.3.8.bb} (93%)