| Message ID | 0101018b96c77f73-e420c509-7b88-4ced-a2cd-bd4936136097-000000@us-west-2.amazonses.com |
|---|---|
| State | New |
| Headers | show |
| Series | [AUH] opencl-headers: upgrading to 2023.04.17 SUCCEEDED | expand |
diff --git a/meta-oe/recipes-core/opencl/opencl-headers_04.17.bb b/meta-oe/recipes-core/opencl/opencl-headers_2023.04.17.bb
similarity index 100%
rename from meta-oe/recipes-core/opencl/opencl-headers_04.17.bb
rename to meta-oe/recipes-core/opencl/opencl-headers_2023.04.17.bb
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *opencl-headers* to *2023.04.17* has Succeeded. Next steps: - apply the patch: git am 0001-opencl-headers-upgrade-04.17-2023.04.17.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 0cd59c2d546257d50e4fc1dc266ae4155d5f890e Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Fri, 3 Nov 2023 17:16:22 +0000 Subject: [PATCH] opencl-headers: upgrade 04.17 -> 2023.04.17 --- .../{opencl-headers_04.17.bb => opencl-headers_2023.04.17.bb} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename meta-oe/recipes-core/opencl/{opencl-headers_04.17.bb => opencl-headers_2023.04.17.bb} (100%)