Hello all you Open, Embedded, and even OpenEmbedded people out there! This is your gentle reminder that we are hosting an OE Workshop in Brussels on Monday, February 6th - the day after FOSDEM at Aven

Hi All, QA for yocto-3.1.22.rc1 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Sum

Hi We are pleased to announce the Yocto Project 4.1.2 Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-4.1.2/poky-74c92e38c701e268406bb656b45ccd68471c217e.

Hello all, I'm in the process of generating an image without GPLv3 software. I have removed everything but the gcc-runtime and libgcc libraries. These are gpl-3.0 with GCC exception. I'm not sure how

Current Dev Position: YP 4.2 M2 Next Deadline: 23rd January 2023 YP 4.2 M2 Build Next Team Meetings: Bug Triage meeting Thursday January 19th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM

Can someone help me with this problem? I want to install chromium on dunfell, and I am receiving this problem. jovanbosic@administrator-ThinkPad-L470:~/Yocto/build$ bitbake core-image-full-cmdline WAR

All, YP M+ or high bugs which moved to a new milestone in WW02 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14960 valgrind ptest fails 12 tests for arm64 target

All, The below were the owners of enhancements or bugs closed during the last week! Who Count alexandre.belloni@... 3 ross.burton@... 1 pavel@... 1 akuster808@... 1 richard.purdie@... 1 Grand Total 7

All, Below is the list as of top 34 bug owners as of the end of WW02 of who have open medium or higher bugs and enhancements against YP 4.2. There are 71 possible work days left until the final releas

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

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.22.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/layer.con

This work has been initiated while discussing issue #14065 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=14065) The topic initially covers ptest reports between releases, but after discussions wi

Hi, I was trying to integrate meta-selinux layer with thud branch on our existing yocto build. I followed all the steps which are mentioned in README and SElinux-FAQ but I am facing an error in do_roo

From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_

From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_

Recent commits have CVE-2022-2741 fixed. Also backported CVE-2022-2993 fix. Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- ...ix-SMP-local-keys-check-when-startin.patch | 51 ++++++++++++++++

oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Drop support for old releases. Signed-off-by: Naveen Saini <naveen.

From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_

When creating recipes for Rust projects, all of the required crates are included in SRC_URI. I need to patch the source of several crates. I've tried creating individual recipes, but that does not rea