similarity index 94%
rename from meta/recipes-kernel/libtraceevent/libtraceevent_1.7.2.bb
rename to meta/recipes-kernel/libtraceevent/libtraceevent_1.7.3.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = "file://LICENSES/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97
file://LICENSES/LGPL-2.1;md5=b370887980db5dd40659b50909238dbd"
SECTION = "libs"
-SRCREV = "1c6f0f3b2bb47571fc455dc565dc343152517d98"
+SRCREV = "dd148189b74da3e2f45c7e536319fec97cb71213"
SRC_URI = "git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git;branch=${BPN};protocol=https \
file://0001-makefile-Do-not-preserve-ownership-in-cp-command.patch"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libtraceevent* to *1.7.3* has Succeeded. Next steps: - apply the patch: git am 0001-libtraceevent-upgrade-1.7.2-1.7.3.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 2457479620ce9827b59c0d449a9081afffcea6fd Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Thu, 15 Jun 2023 22:04:44 +0000 Subject: [PATCH] libtraceevent: upgrade 1.7.2 -> 1.7.3 --- .../{libtraceevent_1.7.2.bb => libtraceevent_1.7.3.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-kernel/libtraceevent/{libtraceevent_1.7.2.bb => libtraceevent_1.7.3.bb} (94%)