Bitbake expects a consistent metadata environment when it parses. There are plenty of ways you can set a recipe to autorev at a point where parts of the fetcher have already been triggered leading to

From: Frederic Martinsons <frederic.martinsons@...> This is related to checksum verification introduction from https://patchwork.yoctoproject.org/project/bitbake/patch/20230315131513.50635-1-frederic.

From: Frederic Martinsons <frederic.martinsons@...> This change brings checksum verification of each crate in a recipe, e.g | SRC_URI += " \ | crate://crates.io/aho-corasick/0.7.20 \ | crate://crates.

From: Frederic Martinsons <frederic.martinsons@...> Signed-off-by: Frederic Martinsons <frederic.martinsons@...> --- lib/bb/fetch2/crate.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --

From: Frederic Martinsons <frederic.martinsons@...> This allow to have classic fetch parameters (like destsuffix, sha256, name ...) not being considered by crate fetcher itself (and so mess up its dow

This patch enables the usage of the '@' character in variable flag names. One use case of variable flags is to indicate and set the namespace of some systemd services/targets. The filenames of systemd

After updating gen_fixtures.py for 'mickledore' 4.2, run './gen_fixutures.py --all' to update oe-core.xml and poky.xml. Drop langdale as support is ending soon. Signed-off-by: Tim Orling <tim.orling@.

Update for 'mickledore' 4.2.0 release and bitbake 2.4 branching. Drop 'langdale' as support will be ending soon. Update stable branches to latest patch release. Signed-off-by: Tim Orling <tim.orling@.

The toaster fixtures need to be updated for each stable release. These should be applied during or shortly after the 2.4 bitbake branching as part of the mickledore 4.2.0 release. Drop langdale since

After updating gen_fixtures.py, run ./gen_fixtures.py --all This includes the latest stable/supported releases. Signed-off-by: Tim Orling <tim.orling@...> --- lib/toaster/orm/fixtures/oe-core.xml | 26

Re-introduce Dunfell since it is supported until April 2024 Drop Honister and Hardknott as they are both EOL Add Langdale as it is the latest stable release Signed-off-by: Tim Orling <tim.orling@...>

We should reference the docs for the current LTS version we are using. Signed-off-by: Tim Orling <tim.orling@...> --- lib/toaster/orm/fixtures/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(

The toaster fixtures need to be updated for each stable release. A similar series was already applied to master, but also needs to be applied to langdale or else toaster is not able to target langdale

When tasks are run with -v (verbose) on the bitbake commandline, shell tasks print their stdout, python tasks do not. This change redirects the python task's print output to an in memory buffer. After

Is there some reason why bitbake started to use tag name identical as branch name from 2.0? It happens only with 2.0 and 2.2, because previous 1.52 branch had first release named 1.52.0 not 1.52: comm

Passed a-full on autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5031 With the exception of a transient failure on oe-selftest-arm due to a temporary outage at gitlab.gn

Passed a-full on autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5030 With the exception of a transient failure on oe-selftest-arm due to a temporary outage at gitlab.gn

Add a function which uses the unshare glibc call to disable networking in the current process. This doesn't work on older distros/kernels but will on more recent ones so for now we simply ignore the c

When tasks are run with -v (verbose) on the bitbake commandline, shell tasks print their stdout, python tasks do not. This change redirects the python task's print output to an in memory buffer. After

From: Richard Purdie <richard.purdie@...> This code appears to be dangerous, it swallows exceptions, turning them into "handled" versions which then show no errors to the user. This is a pretty poor u