I build the image with the command #bitbake phytec-headless-image then I need to add something to the image and I do it like this #rm -rf tmp sstate-cache deploy and #bitbake

<naveen.kumar.saini@...> wrote: This patch is now promoted to zephyr-kernel-src-2.*.1.inc so removing this from zephyr-lvgl fixes this. Ah, yes. This is caused by having ZEPHYR_MODULES in the

Thank you Eilís Ní Fhlannagáin. I faced failures, when I tried to build few recipes: (1) 'zephyr-lvgl' with 'nrf52840dk-nrf52840' machine. Error

if you are using latest release then py2 is more or less not needed unless you use perhaps packages like chromium ( which is also now fixed in meta-browser ) but this is for oe-core and meta-oe

Oops, I just noticed that this was posted to the linux-yocto not the yocto list. I'm BCCing linux-yocto and redirecting the discussion to the yocto list where it's more appropriate. See:

Could you send your patch to the kas mailing list for discussion? It will probably just need a bit tuning on the reasoning: Rootless podman uses fuse-overlayfs for the rootfs, and that seems to

I wouldn't do something like that on purpose :-) Let's see where this goes: https://github.com/siemens/kas/pull/76/commits/eb8f5c90804dee5a1a649883e1d400d1058639b3

Thanks for asking. I wouldn't have minded were you to send this patch without my SoB but if you want you can use foss+yocto@.... The important being that it's fixed ☺️ Cheers, Quentin

Okay. Can I add your SOB line to the patch?

I found information on how to remove python2 from the recipe and add Python3 but I don’t know if/how it will work with NXP. Also, there are a lot of people that say Python2 is needed for

Hi Trevor, To be fair, I didn't take the time to formulate correctly and point to the docs ☺️ podman run --help | grep tmp Does return it though. It's just that some options are specific to

Hey Quentin, Wow not bad, I'm batting 0/2 so far… lol! Curious. When I run "podman -h" on the cmdline it only shows a --tmpdir option $ podman -h | grep tmp --tmpdir string Path to the tmp

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit adds 382 autogenerated machines generated via generate-zephyr-machines.bb. These machines have obviously not all been tested

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> fd8bf397792d58280928d23686313a8da810485a should have also applied the dtc.patch to the 2.6.1 kernel. This commits applies it, so both

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Currently meta-zephyr only checks out a subset of the kernel source. With the addition of being able to generate machine configs

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit removes the need for calling out ZEPHYR_MODULES via MACHINEOVERRIDES. It uses west list to figure out what ZEPHYR_MODULES are

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> We will need west for a few things. First, west knows about all the boards supported, so for automatic machine generation, we will need

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit restructures meta-zephyr into meta-zephyr-core and meta-zephyr-bsp. It moves machine definitions into meta-zephyr-bsp in

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This set of patches relates to what I discussed at https://lists.yoctoproject.org/g/yocto/message/55285. Four major issues (and one

Hi Trevor, https://docs.podman.io/en/latest/markdown/podman-run.1.html#tmpfs-fs I wasn't talking about uids or gids, but pids_limit in containers.conf for podman on your host. See: