sys.exit(0) can cause an error to be reported when the child exits, even though not an error. Since this is a child process, os._exit(0) is the proper way to exit and not cause this

Probably. You'll need to re-send this with a better subject line and commit message so the right people will notice it. Otherwise they'll think it's meta-rockchip-specific. If (when) this patch gets

Applied to meta-rockchip master (with an updated commit message), thanks!

Am 23.09.21 um 22:55 schrieb Trevor Woerner: Could the solution be as simple as this?From b8ba56d84fbac53901e5b7ca122498320e51fbf4 Mon Sep 17 00:00:00 2001From: MarkusVolk

Am 24.09.21 um 15:10 schrieb Trevor Woerner: Thanks for applying :)It would be cool if wic had something like an 'exclude-from-fstab-update" option.That would make the 'fstab-update'

there are different possibilities you have with all great tooling you get with yocto project, I think you have made a good choice. inherently Yocto project is a cross compiling infrastructure so lot

From: Bruce Ashfield <bruce.ashfield@...> 5.13 has been removed from core, and we've moved the default support to 5.14, so we can drop our bbappend. Signed-off-by: Bruce Ashfield

Hi Steven, Please see my comments inline I am a bit confused, but can try to show you what I typically do. In my custom meta-my-layer I add to layer.conf: #--> LICENSE_PATH += "

Thanks for the patch and the SoB line. I'm going to apply this patch, but I'm going to amend the commit message to capture some of the conversation we've had. There's a chance we'll want to know "why"

Ah, good catch. I'm using sysvinit.

Hello: I am running zeus 3.0.4… A vendor has supplied us with a generic license.txt file, which we were able to add to the acexpci recipe we use to build in their package. The license

Am 24.09.21 um 06:46 schrieb Khem Raj: I am using systemd

Yocto has built-in qemu targets for this purpose, and associated infrastructure to start qemu VMs and run tests in them. But to make it practical, these qemu images need to be started on a baremetal

CVE-2021-36086: The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and

Hi, We are starting a new project using Yocto to build a custom Linux image which matches our needs. We are new to Yocto and still trying to figure out the best way to work with it. Especially, if it

Hello Enrico, an eSDK would be enough to do everything, however I would demand the entire development system if I were to start a project, but that is my opinion. I don't know well Node-RED but using

Hello Marco, In your opinion isn't enough to ask for eSDK? for instance if i want to add Node-RED, it would be difficult to build with devtool? because i've seen that it doesn't resolve dependencies

With the eSDK i've to use devtool right?

Hello Enrico, usually nowadays every honest hardware manufacturer provides all the sources of the BSP and the development system to their customers. Try asking your supplier for them. -- Marco

As OE-core explicitly have added depends for qemu-helper addto_recipe_sysroot task, which breaks zephyr-qemuboot implementation of adding build