Current Dev Position: YP 4.1 M2 Next Deadline: 11th July 2022 YP 4.1 M2 Build Next Team Meetings: Bug Triage meeting Thursday June 23rd 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd

minor recipe cleanup Signed-off-by: Armin Kuster <akuster808@...> --- .../{chipsec_git.bb => chipsec_1.8.5.bb} | 21 +++++++++---------- 1 file changed, 10 insertions(+), 11 deletions(-) rename recipes

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/images/security-build-image.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-core/images/security-build-image.bb b/recipes-cor

From: Quentin Schulz <quentin.schulz@...> The patch was meant as a quick temporary work-around to have the docs built and published. Now that releases where -W flag is set (turning warnings into error

Hi all, I'm trying to debug this issue for quite a while but couldn't get any helpful indication on how to solve it. (In case it matters, the build runs on a docker container with shared volumes for S

refresh patch Signed-off-by: Armin Kuster <akuster808@...> --- .../lkrg/files/makefile_cleanup.patch | 72 +++++++------------ ...g-module_0.9.2.bb => lkrg-module_0.9.3.bb} | 7 +- 2 files changed, 30 i

As a first pass, collect all the tmp/buildstats logs using 'cp -a', to enable review and graphing of all builds. The goal is to understand the trends in the /proc/pressure/{cpu|io} data that is now ga

Hi there, I am looking for some kind of package or software, that creates an (USB thumb drive) installer for initial installation and deployment of a yocto image. So you can flash the image onto an US

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Stephen Jolley, Steve Sakoman, Saul Wold, Luca Ceresoli, Michael Opdenacker, Pavel Zhukov, Richard Purdie, Aryaman Gupta, Randy Macleod,

We could do with wider exposure of testing of this so enable on the autobuilder by default. Signed-off-by: Richard Purdie <richard.purdie@...> --- config.json | 3 ++- 1 file changed, 2 insertions(+),

Hi, I'm new to yocto, I wonder the recommended way to setup an environment for yocto using vagrant or docker to isolate from the host, since I've encounter many different error about python version or

Starting with [1] kernel modulus symbols is being slipped in OE-core and this breaks the kernel module sign, so disable it. [1] https://git.openembedded.org/openembedded-core/commit/?id=e09a8fa931fe61

Convert each time-stamped buildstats directory to a compressed tarball using the hostname as a prefix (to the file name only) so that one can identify the source machine. Move these tarballs to the di

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

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

All, The below were the owners of enhancements or bugs closed during the last week! Who Count michael.opdenacker@... 2 ross.burton@... 1 pavel@... 1 richard.purdie@... 1 randy.macleod@... 1 akuster808

All, YP M+ or high bugs which moved to a new milestone in WW26 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 10820 devtool: -d/--debug doesn't show bitbake debug

Hi, I’ve just released the first release of pkgexp, a tool to explore the pkgdata that has been generated in a build. Quoting from the README: pkgexp is a tool to visually explore the OpenEmbedded `pk

Current Dev Position: YP 4.1 M2 Next Deadline: 11th July 2022 YP 4.1 M2 Build Next Team Meetings: Bug Triage meeting Thursday June 30th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd

All, You are cordially invited to the next OpenEmbedded Happy Hour on June 29 for Europe/Americas time zones @ 2100/9pm UTC (5pm ET / 2pm PT). https://www.openembedded.org/wiki/Calendar https://www.op