From: Meh Mbeh Ida Delphine <idadelm@...> Added SPDX identifiers to all .py files except those in migrations directory. Added final new line in all files without it. Fixes: [YOCTO #13527] Signed-off-b

Summary: Build: 20210420-1 had 23 triggers and isn't really worth analyzing. Stay tuned for what is hopefully better data with a higher timeout threshold. There is a nice looking pair of graph attache

There appears to be an issue with build zeus based meta-clang under zeus platform... I followed steps off meta-clang page, and from the work I did with meta-clang under "Rocko" about a year ago, a lot

Yocto Technical Team Minutes, Engineering Sync, for April 20, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/recipes-core/packagegroup/packagegroup-cor

Under ../poky/meta/recipes-devtools the is “llvm”… Devtool search <component> Devtool sdk-install <component> Will add this component to my EXT SDK… Is this a fully functional llvm drop ?, (i.e. is it

Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build Next Team Meetings: Bug Triage meeting Thursday Apr. 22nd at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bF

Working with zeus 3.0.4, extended SDK… Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ? Thanks… When I add in native-python3 support # # Additi

From: Bruce Ashfield <bruce.ashfield@...> A recent fix to the kern-tools promoted some previously unseen issues to warnings. This commit fixes them by tagging some BT options as non-hardware so they w

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, This is the full report for yocto-3.1.7.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone def

Hello, I'm actually migrating a yocto project zeus version to dunfell LTS to build my imx6 Linux system on this LTS release. Almost all works fine except the following message I try to understand when

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