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

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

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,

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

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

Just to clarify, btrfs-tools has always had an LGPL-3.0 library (libbtrfsutil), the recipe just never declared it before. Upstream is relicensing that library to LGPL-2.1+, which should be done for

Hello, We are pleased to announce the Yocto Project 3.3 (hardknott-25.0.0) Release is now available for

+1. Ross <richard.purdie@...> wrote:

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:

Hi Robert, Having the device tree compiler on the target has been useful for me in the past to check the actual content of the device tree using commands such as: * dtc -I fs -O dts

Hi, ethtool can be used to check the network cable connection status and the autonegotiated link speed. That way you can make sure the port was soldered on correctly. Regards, Manuel Am Do, 15. Apr

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

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

Hello , I am experiencing same issue for Rocko build rootfs with QT application for X11. I have tried the solution provided by Max , but it did not worked for me. as Per my log : Using calibration

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

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

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

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

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