linux/poky.git/scripts, branch 5.3_M2

improve_kernel_cve_report: do not use custom version

2025-07-10T09:47:31+00:00

When using the version specified in cve-summary.json, we need to remove the suffix containing the custom version to match the versions from the CVEs. This patch truncates the version from cve-summary.json to use only the base version of the kernel. This is only applicable for kernels where the user has added their own version. (From OE-Core rev: 3942d40e96989268e8d1030f9d8c3859044d9635) Signed-off-by: Daniel Turull Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

improve_kernel_cve_report: do not override backported-patch

2025-07-10T09:47:30+00:00

If the user has a CVE_STATUS for their own backported patch, the backport takes priority over upstream vulnerable versions. (From OE-Core rev: 0beef05be119ea465ba06553a42edea03dfc9fd3) Signed-off-by: Daniel Turull Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

testexport.bbclass oe-test: capture all tests and data from all layers

2025-07-10T09:47:30+00:00

testexport.bbclass only copied files from core layer to the testexport.tar.gz to run tests. Then it filtered out tests and files which were not specified in TEST_SUITES variable. Remove filtering of files to include parselogs.py test data files which are machine and/or layer specific. TEST_SUITES variable is now read from build time exported data store when running tests so there is no need to remove files from exported tests in testexport.bbclass. Adapt oe-test script to find "lib" directories from the new structure with layer specific paths which are used to find tests and test data files. (From OE-Core rev: 5c39fedee1dd0e101e2611b71a895c0251ba968d) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie

devtool: Handle workspaces for multiconfig

2025-07-07T21:12:50+00:00

If a multiconfig recipe is passed to devtool, find the correct workspace name by removing the multiconfig prefix (From OE-Core rev: 42c0c25428be329101a920d31c5fa8cf1e04ee38) Signed-off-by: Joshua Watt Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

recipetool/create_go: proxy module fetching to go-mod-update-modules

2025-07-01T07:49:37+00:00

Now that the go-mod-update-modules class exists, this Go handler can create a stub recipe and then proxy the module handling to the class. (From OE-Core rev: 0aa406d0582d32399c48dfa78f24adc75696112c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe/licenses: move tidy_licenses from recipetool

2025-07-01T07:49:37+00:00

This function, to tidy a license string, is useful outside of recipetool so move it to oe.license. (From OE-Core rev: 9d57b53169bc60b281510c49e54123941a17a8f5) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipetool: create_go: Use gomod fetcher instead of go mod vendor

2025-07-01T07:49:37+00:00

Use the go-mod bbclass together with the gomod fetcher instead of the go-vendor bbclass. (From OE-Core rev: 42b46ab3b92a4f011592e8efcedead075731b8bd) Signed-off-by: Christian Lindeberg Signed-off-by: Richard Purdie

recipetool: allow recipe create handlers to specify bitbake tasks to run

2025-07-01T07:49:37+00:00

When creating a recipe there can be cases where there is a class that does some of the recipe creation (such as cargo-update-recipe-crates). To avoid duplication of code, look for run_task assignments in the extravalues dictionary returned by the handler, and if it is set then call that task after writing the recipe. (From OE-Core rev: 629184de671cf7b86fe95fcce788dffcc3a4da8a) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipetool: create: Support creating extra files named after the recipe

2025-07-01T07:49:37+00:00

(From OE-Core rev: ea26eb8e4a00a63700a95c2c848272b170154294) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

scripts/wic: fix calling wic ls|cp|rm|write hung in bitbake task

2025-06-26T10:02:34+00:00

While calling wic ls/cp/rm/write in bitbake task along with do_image_wic, it hung without return. Due to commit [2255f28b57 wic: add WIC_SECTOR_SIZE variable][1] applied, It calls get_bitbake_var in `wic ls|cp|rm|write' to define sector size. By default, get_bitbake_var starts a `bitbake -e' to get variables which triggers nested bitbake in this situation Refer `wic create', adds option --vars and --image-name to support to read bitbake variables from .env files NOTE: This commit does not add -e for `wic write' to avoid confliction with existed option -e/--expand [1] https://github.com/openembedded/openembedded-core/commit/2255f28b579bc5db4138bcacbb829661ae0ee721 (From OE-Core rev: 793732a6ac2b3788d6c6635e5a496b117bd60584) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie