similarity index 96%
rename from meta/recipes-support/libseccomp/libseccomp_2.5.4.bb
rename to meta/recipes-support/libseccomp/libseccomp_2.5.5.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=7c13b3376cea0ce68d2d2da0a1b3a72c"
DEPENDS += "gperf-native"
-SRCREV = "f33f95014b36f97b42f0c2290e96d5c31647ed10"
+SRCREV = "f0b04ab0b4fc0bc2cde6da1f407b4a487fe6d78f"
SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.5;protocol=https \
file://run-ptest \
@@ -55,4 +55,4 @@ FILES:${PN}-dbg += "${libdir}/${PN}/tests/.debug/* ${libdir}/${PN}/tools/.debug"
RDEPENDS:${PN}-ptest = "coreutils bash"
-PV = "2.5.4"
+PV = "2.5.5"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libseccomp* to *2.5.5* has Succeeded. Next steps: - apply the patch: git am 0001-libseccomp-upgrade-2.5.4-2.5.5.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 bca70412db509f8de3c56342b6a6ea93f9f226e0 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Fri, 15 Dec 2023 13:51:11 +0000 Subject: [PATCH] libseccomp: upgrade 2.5.4 -> 2.5.5 --- .../libseccomp/{libseccomp_2.5.4.bb => libseccomp_2.5.5.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/libseccomp/{libseccomp_2.5.4.bb => libseccomp_2.5.5.bb} (96%)