Thanks for this Sangeeta and team! Since this is final 3.2 we're keen to ensure we sort out the issues we can. There was a buildhistory issue that became apparent in the last few days. Adding in the a

This reverts commit d123606c4bef85c2436b40f51e47b602b7600c0b. This change contains races as it will start poking into do_package task directories from do_populate_sysroot. If we want to do this for na

I'm on record as strongly suggesting PACKAGECONFIG entries should be in the base recipes, there isn't a good reason I'm aware of not to do that. Obviously the system is very flexible though... Cheers,

The fetch error means it can't download the file. The above link: (http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.15.tar.bz2) works for me so it suggests something is wrong with th

bitbake <target name> -c clean should clean up that kind of issue and allow it to continue. Cheers, Richard

The challenge is that we need some kind of functional compiler. You're trying to use a much more modern system that didn't exist when thud was released. Thud is now outside of its support window too.

You could try backporting: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=94b1d77472ad335f26ca4ea6ec8c5b399368c06e Cheers, Richard

In Sakib's defence, did you read the README in pseudo? :) "Discussions and patches should be directed at the openembedded-core mailing list at openembedded-core at lists.openembedded.org." Whether tha

[the original email bounced for some reason, resending to the list] A build flagged for QA (yocto-3.1.3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/rele

lists.yoctoproject.org wrote: Much to my surprise, I figured out the issue and there is a patch for the selftest failure on the bitbake list. It won't stop the release or QA. Cheers, Richard

There were two failures in this build. One was a single selftest failure which I'll look into. The other was a qemumips altcfg image loss of networking. I know Saul is working on better debug for that

You are totally misunderstanding what this variable does. It has nothing to do with images or rootfs. Its also definitely not per recipe. sstate has an overall view of any output 'deployed' in TMPDIR.

You can do the same thing with: do_unpack[depends] += " xorriso:do_populate_sysroot" but note that you want xorriso-native, not xorriso. Cheers, Richard

Signed-off-by: Richard Purdie <richard.purdie@...> --- scripts/utils.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/scripts/utils.py b/scripts/utils.py index 500138d..46346

Signed-off-by: Richard Purdie <richard.purdie@...> --- scripts/utils.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/scripts/utils.py b/scripts/utils.py index 084f575..500138d

From: Michael Halstead <mhalstead@...> Signed-off-by: Michael Halstead <mhalstead@...> Signed-off-by: Richard Purdie <richard.purdie@...> --- scripts/se

Signed-off-by: Richard Purdie <richard.purdie@...> --- config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.json b/config.json index c083b86..19f5c9

Signed-off-by: Richard Purdie <richard.purdie@...> --- config.json | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/config.json b/config.json index a8aa288..c083b86 10

Signed-off-by: Richard Purdie <richard.purdie@...> --- scripts/utils.py | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/scripts/utils.py b/scripts/utils.p

On stable release branch builds, it will clone "master" since comparebranch is None. It will then fail to push since there is already a dunfell branch upstream with changes on which it needs to rebase