Signed-off-by: Jose Quaresma <quaresma.jose@...> --- ...streamer1.0-vaapi_1.18.5.bb => gstreamer1.0-vaapi_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Jose Quaresma <quaresma.jose@...> --- ...ugins-ugly_1.18.5.bb => gstreamer1.0-plugins-ugly_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Jose Quaresma <quaresma.jose@...> --- ...plugins-bad_1.18.5.bb => gstreamer1.0-plugins-bad_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Jose Quaresma <quaresma.jose@...> --- ...ugins-good_1.18.5.bb => gstreamer1.0-plugins-good_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Jose Quaresma <quaresma.jose@...> --- ...ugins-base_1.18.5.bb => gstreamer1.0-plugins-base_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Jose Quaresma <quaresma.jose@...> --- .../{gstreamer1.0_1.18.5.bb => gstreamer1.0_1.18.6.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Update the test to match the renamed license in the recipe. Signed-off-by: Richard Purdie <richard.purdie@...> --- meta/lib/oeqa/selftest/cases/bbtests.py | 4 ++-- 1 file changed, 2

This is a security fix release containing fixes for CVE-2022-25235, CVE-2022-25236, CVE-2022-25313, CVE-2022-25314 and CVE-2022-25315. Signed-off-by: Richard Purdie

The threading code here can race as the fetcher changes the environment which is shared between the threads. By setting it up in advance, it isn't changed and therefore no longer

Hi, This looks interesting and is improving, thanks. I haven't done a full review on it but as I glanced through it, I had some questions. See inline below. Why do we patch some tests out but

The patch implements Oe-selftest framework for Rust test. Some of the functions are as follows:- setup_cargo_environment(): Build bootstrap and some early stage tools. do_rust_setup_snapshot():

I re-ran the test and got the same error, so it doesn't seem to be intermittent. Thanks! Steve

Yep, I'll poke at that. Andrew

I'm not sure I agree with that. I get the feeling some people want to allow these packages as long as they're with license X. Licenses can change over time and this allows a safety net that if it

I saw this on qemux86-64, but was not sure it was due to the upgrade or a one off infra issue. I’ll dig deeper and see what might be happening.

I'm seeing ptest errors: WARNING: core-image-sato-sdk-ptest-1.0-r0 do_testimage: There were failing ptests. Traceback (most recent call last): File

Warning: wall of text ahead. Sorry about that, but I believe it is important that we get this right if we are redesigning it. TL;DR: see the end for the new suggested licensing variables.

this is bugfix release https://github.com/libgit2/libgit2/releases/tag/v1.4.1 Signed-off-by: Khem Raj <raj.khem@...> --- .../libgit2/{libgit2_1.4.0.bb => libgit2_1.4.1.bb} | 4 ++--

Folks, As a follow-on to yesterday's email and replies, I would like to make the following proposal for dealing with the changes to INCOMPATIBLE_LICENSE and associated variables. Current