The default behavior is to look for a bitbake command, which fails and produces a confusing output of [-1:]. [YOCTO #14208] Signed-off-by: Yi Fan Yu <yifan.yu@...> --- scripts/utils.py | 3 +++ 1 file

This is the default oe-core MACHINE value. Prevent error-reporting tool to report simply False. It was seen in check-layer where the MACHINE wasn't specified. [YOCTO #14208] Signed-off-by: Yi Fan Yu <

All, YP M+ or high bugs which moved to a new milestone in WW16 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14334 open-vm-tools not present in layer index randy.ma

All, The below were the owners of enhancements or bugs closed during the last week! Who Count ross@... 2 akuster808@... 2 randy.macleod@... 2 richard.purdie@... 1 Grand Total 7 Thanks, Stephen K. Joll

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

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 the

btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build, remove the dependency from its ptest package. This may regress some ptests but keeps the gplv2 layer working. Signed-off-by: Richar

Hello, We are pleased to announce the Yocto Project 3.3 (hardknott-25.0.0) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/poky-hardknott-25.0.0.tar.b

for a current project (and subsequent projects), i want to define a hardware bringup image; that is, a really basic image chock-full of low-level utilities for debugging initial board bringup. this me

Hi all, I recently upgraded my project from dunfell 3.1.5 to 3.1.6 and saw errors about pseudo path mismatches on various build machines. Removing TMPDIR solved the problem, but I did some digging to

Hello, We are experiencing a build failures only on our build servers, but not using the same containerised build environment locally, which is confusing to say the least. We have already tried the nu

Hello I have built the Yocto gatesgarth image for Beaglebone black. Then I loaded the image in SD card and booted with beagle. Is there any way to check whether the image is built and working with bea

Hello, I have been working on Rocko build from fsl-community-bsp, since last few days and able to complete the builds for our various devices which uses imx6UL and imx6Solo processors. During testing

From: Ming Liu <liu.ming50@...> Introduce IMA_FORCE to allow the IMA policy be applied forcely even 'no_ima' boot parameter is available. This ensures the end users have a way to disable 'no_ima' supp

From: Ming Liu <liu.ming50@...> IMA_POLICY is being referred as policy recipe name in some places and it is also being referred as policy file in other places, they are conflicting with each other whi

From: Ming Liu <liu.ming50@...> This ensures when a end user change the IMA_EVM_X509 key file, ima-evm-keys recipe will be rebuilt. Signed-off-by: Ming Liu <liu.ming50@...> Signed-off-by: Armin Kuster

From: Ming Liu <ming.liu@...> Ming Liu (3): ima-evm-keys: add file-checksums to IMA_EVM_X509 meta: drop IMA_POLICY from policy recipes initramfs-framework-ima: introduce IMA_FORCE .../initrdscripts/in

I attempted to add llvm to my zeus image, and I am seeing the following Yocto build error… What is the actual problem here, and how best resolve ? Build Configuration: BB_VERSION = "1.44.0" BUILD_SYS

My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more then enough with 4 core + HT, but now

With the previous interval of 10 seconds, there would be serveral times when the system was very busy and the script would not return before the next run was scheduled resulting in no measurement. In