There’s an open issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6434 The easiest implementation would be a rootfs-time postprocessing step where you compile every .py file, and then delete

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

I don't remember any such discussion. If you want this to happen, you are welcome to develop the feature. Alex

Hi, I was wondering if there has been talk about support for source-less python on an image. Installing py and pyc files doubles the size of python on the rootfs. I can imagine this being implemented

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

The NAS couldn't cope with the number of small files these data trees contained leading to timeouts. If you want to do something like this you'll probably have to create tarball archives of the

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

It’s linker cmdline which is interesting here please post it and that will help to see further

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

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at

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

Hello Quentin, Richard and I eventually did that: disabling the errors on warnings, so that we can make progress on the Sphinx updates and the generation of epub and pdf formats. This won´t prevent

From: Michael Opdenacker <michael.opdenacker@...> This allows to switch to a more recent of Sphinx which will generate warnings with old versions of docs. This way, it's not immediately

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

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(-)

We use the ability to regenerate previous releases to update the switcher lists and potentially other style related changes in future which keeps the docs looking consistent. We may have to disable

Hi Quentin We're trying to build the docs with Sphinx 5.0.0 on a special branch, and we're getting warnings causing the builds to fail:

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

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 2 ++ recipes-security/Firejail/firejail_0.9.70.bb | 2 ++ 2 files changed,

All, YP M+ or high bugs which moved to a new milestone in WW25 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 5322 Global DNS fallback mechanism not