linux/poky.git/meta/classes, branch yocto-3.4.3

crate-fetch: fix setscene failures

2022-03-24T11:05:16+00:00

In sstate.bbclass, when fetching an sstate object we have: pstaging_fetch(sstatefetch, d): [...] localdata.setVar('SRCPV', d.getVar('SRCPV')) i.e. some code which expands SRCPV before it changes SRC_URI for the sstate tarball fetching. In crate-fetch.bbclass we have: def import_crate(d): import crate if not getattr(crate, 'imported', False): bb.fetch2.methods.append(crate.Crate()) crate.imported = True def crate_get_srcrev(d): import_crate(d) return bb.fetch2.get_srcrev(d) SRCPV = "${@crate_get_srcrev(d)}" and so an "import crate" occurs when pstating_fetch() is called. That succeeds and all is well but the bb.fetch2.get_srcrev(d) call fails since there is no url in SRC_URI which supports srcrev() resulting in: | WARNING: rust-cross-core2-32-musl-1.54.0-r0 do_deploy_source_date_epoch_setscene: ExpansionError('SRCPV', '${@crate_get_srcrev(d)}', FetchError('SRCREV was used yet no valid SCM was found in SRC_URI', None)) | WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rust-cross-core2-32-musl/1.54.0-r0/temp/log.do_deploy_source_date_epoch_setscene.3133099 | WARNING: Setscene task (/home/pokybuild/yocto-worker/musl-qemux86/build/meta/recipes-devtools/rust/rust-cross_1.54.0.bb:do_deploy_source_date_epoch_setscene) failed with exit code '1' - real task will be run instead [YOCTO #14680] (From OE-Core rev: 73b6c53ceea30a3f81c6de88c5bea452fe1c0018) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

sstate: inside the threadedpool don't write to the shared localdata

2022-03-15T16:38:28+00:00

When inside the threadedpool we make a copy of the localdata to avoid some race condition, so we need to use this new localdata2 and stop write the shared localdata. (From OE-Core rev: b6893ed80df90b0e9468f291205f38cc76960e08) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie (cherry picked from commit 1fa763b2022822a76fde541724e83e1977833d03) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

rootfs-postcommands: amend systemd_create_users add user to group check

2022-03-10T16:39:50+00:00

Currently when adding a user to a group ('m' type), the conditional check to only create a user/group if it does not exist always resolves to true. This causes a build exit failure if the user and/or group defined in the sysusers configuration file were already created prior to the execution of systemd_create_users(). This logic has been updated to instead fail silently (consistent with 'u' and 'g' type). Additionally, if a user doesn't exist it will be created without the default group. (From OE-Core rev: 5f53e232f92011e131abff6128fa25812c3744ac) Signed-off-by: Tean Cunningham Signed-off-by: Richard Purdie (cherry picked from commit 65649be6b2196ab964c69605d0306bfc2481da33) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

Revert "cve-check: add lockfile to task"

2022-03-10T16:39:50+00:00

Now that all of the functions in cve-check open the database read-only, we can remove this lockfile. This means cve-check can run in parallal again, improving runtimes massively. This reverts commit d55fbf4779483d2cfd71df78d0f733b599fef739. (From OE-Core rev: ecec5339a35f0578669642fc72cbaad2f83bb272) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit d3d3e7b324698ec3e6fce1951aba389805f3edd3) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

cve-check: get_cve_info should open the database read-only

2022-03-10T16:39:50+00:00

All of the function in cve-check should open the database read-only, as the only writer is the fetch task in cve-update-db. However, get_cve_info() was failing to do this, which might be causing locking issues with sqlite. (From OE-Core rev: 3c79237085169b96cc56910b08263437cad09e4d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 8de517238f1f418d9af1ce312d99de04ce2e26fc) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

default-distrovars.inc: Switch connectivity check to a yoctoproject.org page

2022-02-24T11:12:39+00:00

example.com is proving unreliable at present so switch to our own connectivity page instead. That page is very simple avoiding app overhead on our web server which was an original reason for switching to example.com. (From OE-Core rev: 83543d4576284a1a437cbc42ebe84b8639068143) Signed-off-by: Richard Purdie (cherry picked from commit dc6b043cb75c5751b5a98afd2201aa31f9b4b9f6) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

qemuboot: Fix build error if UNINATIVE_LOADER is unset

2022-02-24T11:12:39+00:00

I got this error on current master: File: 'exec_func_python() autogenerated', lineno: 2, function: 0001: *** 0002:do_write_qemuboot_conf(d) 0003: File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 141, function: do_write_qemuboot_conf 0137: else: 0138: val = d.getVar(k) 0139: # we only want to write out relative paths so that we can relocate images 0140: # and still run them *** 0141: if val.startswith(topdir): 0142: val = os.path.relpath(val, finalpath) 0143: cf.set('config_bsp', k, '%s' % val) 0144: 0145: # QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a symlink Exception: AttributeError: 'NoneType' object has no attribute 'startswith' Do nothing if "val" is None, which may happen for k = "UNINATIVE_LOADER". (From OE-Core rev: d59dd9098224e93cf866ddbb618cadcb1021fa63) Signed-off-by: Zoltán Böszörményi Signed-off-by: Richard Purdie (cherry picked from commit 020043c16ce25238313cbf0d10e40e9f6551bf14) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

cve-check: create directory of CVE_CHECK_MANIFEST before copy

2022-02-24T11:12:39+00:00

Create directory of the CVE_CHECK_MANIFEST variable before copy to it, so that the variable can use an arbitrary directory name. (From OE-Core rev: 74888f3ba0c31d635930d94b066750e5440cc906) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie (cherry picked from commit 9829c16301bf2dce39fa046401a984f112fa0322) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

sstate: Improve failure to obtain archive message/handling

2022-02-09T23:15:15+00:00

The bb.fatal() case where sstate failed to find/use an archive in setcene tasks is suboptimal. Bitbakes handling of setscene tasks will be to warn but the fatal will turn this into an error, despite the real task being rerun. In these failure cases other messages would usually have been printed so turn this into a warning and raise a handled exception status so that bitbake knows to fail the task but not print more messages. (From OE-Core rev: 25a7e8dae10dde6073dcdd80f1e2448b59dc9d1a) Signed-off-by: Richard Purdie (cherry picked from commit 7875baeca7a3ed216b2442fb8771e51efbfa5a4f) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

insane.bbclass: Correct package_qa_check_empty_dirs()

2022-02-09T23:15:15+00:00

The oe.qa.add_message() method is not available in Honister, use package_qa_add_message() instead. (From OE-Core rev: 3f183a7f5b4704b32bd094d5ebbe8584ce26ae34) Signed-off-by: Peter Kjellerstedt Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie