linux/poky.git/meta/lib, branch yocto-3.1.7

populate_sdk_ext: Avoid copying and producing .pyc files

2021-04-06T21:45:36+00:00

Since pyc cache files are really system specific, no real reason to copy or generate them during the eSDK build process. Also generating them has the possibility of re-using inodes that pseudo may have been tracking, leading a build failure. (From OE-Core rev: e3d027b48bf54fef9420cd1cd4f04a9bedf8d032) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie (cherry picked from commit ce8eba263647ae63a722122e28f26af46ae083a0) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

selftest/wic: Fix dependency issue in rawcopy test

2021-03-28T21:31:47+00:00

The current test code contains a subtle race. It is building an ext4, then trying to reuse that image in a wic build for the same recipe. Whilst this happened to work, the code is within its rights to clean up the output before the wic code runs. Avoid this by using separate image targets instead. (From OE-Core rev: d30a90062e29a3069f6e8d9f6d4eadd7a48adf4f) Signed-off-by: Richard Purdie (cherry picked from commit 590398080e81fb5e2f81e12b8900858837dfe25f) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cve-check: CVE_VERSION_SUFFIX to work with patched release

2021-03-28T21:31:47+00:00

CVE_VERSION_SUFFIX in "patch" to treat version string with suffix "pX" or "patchX" as patched release. also update testcases to cover this changes and set CVE_VERSION_SUFFIX for sudo. (From OE-Core rev: d75f95a09e5e85eb759e748f9e0fee1c5fa1b318) Signed-off-by: Lee Chee Yang Signed-off-by: Richard Purdie (cherry picked from commit 8076815fc2ffc8f632e73527ce2b7d158a29e9ea) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

Revert "sstatesig.py: show an error instead of warning when sstate manifest isn't found"

2021-03-28T21:31:46+00:00

Causes breakage in other layers This reverts commit e0c1db170fdd6c1d78fdfce017feae26c96fac29. Signed-off-by: Richard Purdie

bitbake-bblayers/create: Fix incorrect priority help message

2021-03-18T21:20:25+00:00

The help message for the optional argument of setting the priority of the new layer was incorrect. (From OE-Core rev: 4557255a95f9aac8c1e955c078ca05f995c1299c) Signed-off-by: Charlie Davies Signed-off-by: Richard Purdie (cherry picked from commit d10d928c6030951994bc2404cde78137c86917a4) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/pam: Need shadow installed for the tests

2021-03-18T21:20:25+00:00

Distros may not use shadow for login manager secondly login --help returns 1 only with shadow provided login utility, with busybox it returns normal 0, the testcase clearly assumes shadow being part of image, therefore add needed checks to ensure the pre-requisites are met (From OE-Core rev: 0ac2dee8756573a793af56582565f221ff6b93c5) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie (cherry picked from commit 0820aeba74869bf6e85b200f39bc610a43ab9a7a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

selftest/reproducible: Add ability to pull some objects from sstate

2021-03-18T21:20:24+00:00

When debugging why a single recipe doesn't reproduce, its a pain to wait for the world to rebuild from scratch. Update the selftest to allow this to be configured, for example you could set targets as ['perf'] and sstate_targets as ['virtual/kernel'] and then it should only be rebuilding perf in the test rather than things like the toolchain (parts of the kernel may be unavoiable as they're not in sstate). Can be run as: OEQA_DEBUGGING_SAVED_OUTPUT=/tmp/perf-diffoscope oe-selftest -r reproducible.ReproducibleTests.test_reproducible_builds to save diffoscope output. (From OE-Core rev: 8b38cd1b36f3e227a63c0aa3955f3f5ab172c509) Signed-off-by: Richard Purdie (cherry picked from commit 132a17d02f29711572e14a2f38a841323fbb6df6) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

reproducible: Improve SOURCE_DATE_EPOCH_FALLBACK handling

2021-03-10T00:22:51+00:00

Ensure the fallback value if used is written to the SDE file and hence stored in sstate, reducing any confusion within the code over '0' values. Bump the HASHEQUIV_VERSION since we've had a ton of trouble with ensuring this rolls out correctly on the autobuilder so others may too, take a clean slate for it. (From OE-Core rev: 1f218351c2ef702c76b1d1e793a624e1a4f5079b) Signed-off-by: Richard Purdie (cherry picked from commit 53ffffa32b76330835287dfc05d4e4796841af08) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

sstatesig.py: show an error instead of warning when sstate manifest isn't found

2021-03-10T00:22:50+00:00

* not sure if there are some valid use-cases for missing manifest, but recently I'm seeing increasing number of build failures where something from native recipe is missing (seen it with pseudo, autoconf, nodejs recently) and the only indication that something is wrong (before showing sometimes misleading error like: recipe-sysroot-native/usr/bin/node: No such file or directory is this warning: NOTE: Running task 7844 of 12431 (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_prepare_recipe_sysroot) NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Started WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot not found in x86_64 x86_64_ubuntu-18.04 (variant '')? NOTE: Running task 7845 of 12431 (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_unpack) NOTE: recipe nodejs-12.20.2-r0: task do_unpack: Started WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot not found in x86_64 x86_64_ubuntu-18.04 (variant '')? NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Succeeded if I rebuild that native dependency, then it gets fixed and I don't see these failures in clean builds (as without sstate and with empty TMPDIR), only in incremental builds * but if there isn't valid reason for missing manifest file, then I think it would be better to error early (or even bb.fatal()) (From OE-Core rev: e0c1db170fdd6c1d78fdfce017feae26c96fac29) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit 95607a26854d873399d2b9d7e5fcbffc0cbdba4c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

selftest/reproducible: Don't call sync between each file compare

2021-03-04T17:39:10+00:00

Calling sync between each file compare is horrible performance wise as we compare thousands of files. We don't care about IO latency here so disable. (From OE-Core rev: dd893279f352e290c23577a0f91df1b8c6232f10) Signed-off-by: Richard Purdie (cherry picked from commit 25f78abd8bbeb201fd9452e7983e015027954948) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie