similarity index 91%
rename from meta/recipes-support/liburcu/liburcu_0.15.3.bb
rename to meta/recipes-support/liburcu/liburcu_0.15.4.bb
@@ -13,7 +13,7 @@ LIC_FILES_CHKSUM = "file://LICENSE.md;md5=c2a92498b6e88e276f986877995425b8 \
SRC_URI = "http://lttng.org/files/urcu/userspace-rcu-${PV}.tar.bz2"
-SRC_URI[sha256sum] = "26687ec84e3e114759454c884a08abeaf79dec09b041895ddf4c45ec150acb6d"
+SRC_URI[sha256sum] = "11a14a7660ac9ba9c0bbd3b2d81718523d27dc6c8a9dfabd5e401b406673ee3a"
S = "${UNPACKDIR}/userspace-rcu-${PV}"
inherit autotools multilib_header
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *liburcu* to *0.15.4* has Succeeded. Next steps: - apply the patch: git am 0001-liburcu-upgrade-0.15.3-0.15.4.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 74759f5977112c23b937ef17b3c7bf016dd3badd Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Wed, 5 Nov 2025 23:08:50 +0000 Subject: [PATCH] liburcu: upgrade 0.15.3 -> 0.15.4 --- .../liburcu/{liburcu_0.15.3.bb => liburcu_0.15.4.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/liburcu/{liburcu_0.15.3.bb => liburcu_0.15.4.bb} (91%)