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

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

sstate: A third fix for for touching files inside pseudo

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

This continues where commit676757f "sstate: fix touching files inside pseudo" and commit 29fc8599 "sstate: another fix for touching files inside pseudo" left off. The previous changes switched from trying to check if the sstate file is writable before touching it, to always touching the sstate file and ignoring any errors. However, if the sstate file is actually a symbolic link that links to nothing, this would actually result in an empty sstate file being created. And this in turn leads to that future setscene tasks will fail when they try to unpack the empty file. Change the code so that if an sstate file linking to nothing already exists, it is overwritten with the new sstate file. Also change it so that the temporary file that is used is always removed, even if ln fails to link the sstate file to it. (From OE-Core rev: b2a5d9bc61e0b2b7e0f187a262a514952ed30563) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

rootfs-postcommands.bbclass: Make two comments use the new variable syntax

2022-01-19T11:11:58+00:00

(From OE-Core rev: 5293916ac660c4cfd6304826fb10de1454a40bf5) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit cb17cccaf2f51558bd1d320559bd792d5869688e) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

cve-check: add lockfile to task

2022-01-19T11:11:57+00:00

this should prevent running into the very rare error sqlite3.OperationalError: attempt to write a readonly database As highlighted by https://www.sqlite.org/faq.html#q5 it is likely that the adapter won't allow use multiple exec calls at the same time. So it's best to prevent multiple accesses at a time, by reusing the already in place CVE_CHECK_DB_FILE_LOCK YOCTO #14110 (From OE-Core rev: 53dc9b10eb5f064c68120337126f1542c1e0c832) Signed-off-by: Konrad Weihmann Signed-off-by: Richard Purdie (cherry picked from commit 677f5741bd265be49d4a5bb933b3e8d8c4eec653) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

license.bbclass: implement ast.NodeVisitor.visit_Constant

2021-12-17T10:02:40+00:00

Since Python 3.8 visit_Num(), visit_Str() and so on are all deprecated and replaced with visit_Constant. We can't yet remove the deprecated functions until we require 3.8, but we can implement visit_Constant to silence the deprecation warnings. (From OE-Core rev: 067fbe5e12a81225cf3ff436837af6a6d23040a6) Signed-off-by: Ross Burton Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

uboot-sign: fix the concatenation when multiple U-BOOT configurations are specified

2021-12-17T10:02:39+00:00

Some BSPs, especially those of meta-freescale and meta-ti allow to build U-Boot binaries using different configuration for a given target, for example: - UBOOT_CONFIG ??= "tfa-secure-boot tfa" - UBOOT_CONFIG ??= "nand sdcard spi nor" When this is the case the public key wasn't concatenated to all U-Boot binaries built. (From OE-Core rev: e9f8162e619af05077eb5a30089cdbdcf309c161) Signed-off-by: Thomas Perrot Signed-off-by: Alexandre Belloni (cherry picked from commit dfd71ae3d102f3010c6117d774e9739a322930f6) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

buildhistory: Fix srcrevs output

2021-12-13T23:02:49+00:00

The code was assuming that the a recipe with only one srcrev wouldn't "name" it. This isn't the case as the glibc or bzip2 recipes show, you can have a single srcrev which is named. We can pull the data from the fetcher and in fact we already have it, we just need to handle the "default" case and make that code the default for all srcrev regardless of length. [YOCTO #14017] (From OE-Core rev: 8b6e565afcfb73a33e3759486554365798e74d66) Signed-off-by: Richard Purdie (cherry picked from commit 45ae567932ba52b758eb41754453e9828d9533a1) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

classes/crate-fetch: Ensure crate fetcher is available

2021-12-13T23:02:49+00:00

Reworks the crate fetcher class to have it install the fetcher at recipe finalization so that it is always available before SRC_URI is expanded. In addition, override the value of SRCPV to also install the fetcher when SRCPV is expanded so that AUTOREV works. [YOCTO #10867] (From OE-Core rev: 19577427d25739588fdf607b6e3905dddfe206ff) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie (cherry picked from commit bc66c5dd65fb654af5cd91b47f9b4f7a5f53436e) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

rootfs-postcommands: update systemd_create_users

2021-12-13T23:02:49+00:00

Process all systemd-sysusers configuration files in order to create users/groups at build time. systemd-sysusers would try to create them at run-time, but for read-only rootfs that's not possible and results in warnings from different services: systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:39 Unknown group 'render', ignoring systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:42 Unknown group 'sgx', ignoring (From OE-Core rev: c25d9d2dae45805fa985f1c541cacfb0230f9522) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Richard Purdie (cherry picked from commit f86ffdb1b77c6ba32ec250545a40c1c54f983f21) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie