* move it from kernel.bbclass, because it needs to stay in sync with IMAGE_LINK_NAME structure * image-artifact-names.bbclass is also inheritted from kernel-artifact-names.bbclass so every recipe whic

* this still assumes that IMAGE_LINK_NAME will contain IMAGE_BASENAME which will be BPN 'multiconfig-image-packager' and that replacing it with 'core-image-minimal' will match with the actual IMAGE_LI

* this one is more tricky, because the test_rawcopy_plugin.wks.in file is used while building core-image-minimal-mtdutils, but the image filename inside wks.in is from core-image-minimal, so we cannot

* don't assume that every built image is named: <recipe>-<machine>.<suffix> [YOCTO #12937] Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/lib/oeqa/selftest/cases/runqemu.py | 10 ++++++-

* use IMAGE_LINK_NAME instead of hardcoding core-image-minimal-${MACHINE} assumption [YOCTO #12937] Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/lib/oeqa/selftest/cases/wic.py | 38 ++

* with my build/conf/local.conf: SSTATE_DIR = "/OE/build/poky/build/sstate-cache" these devtool tests will first set own SSTATE_DIR and the original one set as SSTATE_MIRROR: 2023-03-11 11:51:46,837 -

* this is one of the failures from distrodata.Distrodata.test_checkpkg: 2023-03-11 14:26:21,482 - oe-selftest - INFO - ====================================================================== 2023-03-11

These changes are preparation for the actual changes from [YOCTO #12937], but without changing anything in current artifacts naming schema. Only change outside selftest was moving of INITRAMFS_IMAGE_N

* avoid copying whole exec_prefix over base_prefix as there were only zoneinfo files anyway Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/recipes-extended/timezone/tzdata.bb | 14 +++++

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/recipes-extended/timezone/timezone.inc | 6 ++++-- meta/recipes-extended/timezone/tzcode-native.bb | 3 --- meta/recipes-extended/timezone/t

Hi Lukas, and update on this series? It doesn't have to be perfect, other people can help with remaining corner cases and right now there is nothing for this in oe-core, so any version will be big imp

Major ffmpeg upgrade might not be risky for components in oe-core (as you've already patched gst-libav). But considering how many other projects are still using ffmpeg-4, because upgrade to ffmpeg-5 a

Sorry, didn't get enough coffee today, I was reading it wrong.

- local vname="_$1" - fi + local vname="$1" cat <<EOF > ubinize${vname}-${IMAGE_NAME}.cfg _ surely got removed from this ubinize filename, right?

Acked-by: Martin Jansa <Martin.Jansa@...>

On Thu, Mar 9, 2023 at 8:55 AM Romuald Jeanne via lists.openembedded.org <romuald.jeanne=st.com@...> wrote: Did you drop the _ separator intentionally?

On Tue, Feb 28, 2023 at 10:52 AM Michael Opdenacker via lists.openembedded.org <michael.opdenacker=bootlin.com@...> wrote: Whole BACKFILL mechanism was added for easier backwards co

As the network evaluation patch was merged in bitbake: https://git.openembedded.org/bitbake/commit/?id=3d96c07f9fd4ba1a84826811d14bb4e98ad58846 I can send my inline version: https://git.openembedded.o

From: Joel Stanley <joel@...> When building native qemu with 6.2 kernel headers, qemu fails to build: In file included from /usr/include/linux/btrfs.h:29, from ../qemu-7.2.0/linux-user/syscall.c

Can you confirm if it was related to glibc upgrade for you or it might be kernel headers like for me and it just looked like glibc related?