Yocto Technical Team Minutes, Engineering Sync, for July 13, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made

Hi Samuel Please look at insane.bbclass and perhaps a new check can be added there ?

.snip. Hi Lei, I tried the latest meta-spdxscanner with a Docker version cof Fossology but the entire process fails with errors on the Yocto bitbake side. I'd like to have a minimal proof of work of

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday July 15th at 7:30am PDT

All, YP M+ or high bugs which moved to a new milestone in WW28 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11906 rpmbuild: Can not build packages on

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 3 akuster808@... 2 ross@... 2 thomas.perrot@... 1 mshah@... 1 Grand

All, Below is the list as of top 50 bug owners as of the end of WW28 of who have open medium or higher bugs and enhancements against YP 3.4. There are 77 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Rather than just ppc/mips, use the pregen-hostkeys on all the qemu targets since this is using a lot of time on the autobuilders when we don't really need to. This should avoid some of the testing

Hi Lei, thank you for answering. Considering the problems I encounter with scancode-tk and that the artifacts it produces are simple text files that need further analysis, I was just deciding to

Hi Marco Yes, you can contact me or contribute to meta-spdxscanner to this ML. I have not maintained scancode-tk for long time. And recently there are somebody else asked me about scancode-tk. Yes,

Hi everyone, I was asked to add some basic tests to an internal recipe in order to improve our CI system. The purpose would be to produce an error if some check doesn't pass like - a file is not

We have many recipes appended to IMAGE_INSTALL in our image recipes and it works just fine. From your description, it sounds like you could go either way. I personally prefer to keep my image recipes

sorry about that, right now the config files are placed in the files directory of the recipe which builds the module. Sample snippets of the recipe concerning this config file, I removed the rest of

You left a few details out about how the configuration files are managed. Ideally you could just make bitbake recipes for the config files themselves. This way you can create an image recipe for each

Hi everyone, I'm curious on a good approach when dealing with multiple projects I've just started out yocto and have already created our own meta-layer which contains our modules. Now these modules

add Paul Eggleton

From: Changqing Li <changqing.li@...> Now, YPCompatibleVersions's name is only designed for using version like 2.0 3.0, the max_length is 25. but we mostly use Codename for

I'm using Zeus. I'm trying to create and mount a data partition using wic. My wks file is part u-boot --source rawcopy --sourceparams="file=u-boot.imx" --ondisk mmc --no-table --align 1 part /boot

You are right that it's not actually a percentage and is instead tied to the number of cores. I'll correct the patch body to reflect this when I inevitably send a v2. With the latest testing on