From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, quirin.gylstorff@siemens.com
Subject: Re: [PATCH 0/2] Rework deployment of image artifacts
Date: Thu, 16 Apr 2026 17:42:48 +0200 [thread overview]
Message-ID: <9da6af9d-c17c-4d75-9085-a77c5f970e0a@ilbers.de> (raw)
In-Reply-To: <20260410132250.3320171-1-felix.moessbauer@siemens.com>
Applied to next, thanks.
Zhihang
On 4/10/26 15:22, Felix Moessbauer wrote:
> As the changing of the DEPLOY_DIR_IMAGE has proven to be fundamentally
> incompatible with custom initrd recipes, this patch was reverted,
> re-introducing the do_copy_boot_files error on DTBs that are named
> equally but belong to different mc targets.
>
> This series mitigate the issue by keeping the layout of DEPLOY_DIR_IMAGE,
> but prefixing the DTB_FILES with PN and DISTRO. These prefixes are
> then stripped again during imaging.
>
> Note, that the series has been CI tested against the "dtbdeploy" and "dev"
> tags.
>
> Best regards,
> Felix Moessbauer
> Siemens AG
>
> Felix Moessbauer (2):
> Revert "meta: Deploy image build artifacts into distro- and
> image-specific subdirs"
> prefix DTB files with PN in deploy dir
>
> RECIPE-API-CHANGELOG.md | 84 +++----------------
> .../installer-add-rootfs.bbclass | 9 +-
> meta/classes-recipe/image.bbclass | 17 ++--
> .../imagetypes_container.bbclass | 2 +-
> meta/classes-recipe/imagetypes_wic.bbclass | 2 +-
> meta/conf/bitbake.conf | 3 +-
> .../wic/plugins/source/bootimg-efi-isar.py | 3 +-
> .../plugins/source/isoimage-isohybrid-isar.py | 2 +-
> testsuite/cibase.py | 2 +-
> testsuite/citest.py | 7 +-
> testsuite/start_vm.py | 2 +-
> 11 files changed, 36 insertions(+), 97 deletions(-)
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/9da6af9d-c17c-4d75-9085-a77c5f970e0a%40ilbers.de.
next prev parent reply other threads:[~2026-04-16 15:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:22 'Felix Moessbauer' via isar-users
2026-04-10 13:22 ` [PATCH 1/2] Revert "meta: Deploy image build artifacts into distro- and image-specific subdirs" 'Felix Moessbauer' via isar-users
2026-04-10 13:22 ` [PATCH 2/2] prefix DTB files with PN in deploy dir 'Felix Moessbauer' via isar-users
2026-04-10 13:38 ` 'Jan Kiszka' via isar-users
2026-04-10 14:12 ` 'MOESSBAUER, Felix' via isar-users
2026-04-10 16:32 ` 'Jan Kiszka' via isar-users
2026-04-16 13:54 ` Zhihang Wei
2026-04-16 14:39 ` 'MOESSBAUER, Felix' via isar-users
2026-04-16 15:41 ` Zhihang Wei
2026-04-10 14:21 ` [PATCH 0/2] Rework deployment of image artifacts Zhihang Wei
2026-04-16 15:42 ` Zhihang Wei [this message]
2026-04-16 15:51 ` 'Jan Kiszka' via isar-users
2026-04-16 16:01 ` 'Jan Kiszka' via isar-users
2026-04-17 14:15 ` Zhihang Wei
2026-04-17 14:39 ` 'Jan Kiszka' via isar-users
2026-04-17 15:05 ` 'Jan Kiszka' via isar-users
2026-04-20 6:25 ` 'Quirin Gylstorff' via isar-users
2026-04-20 16:00 ` Zhihang Wei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9da6af9d-c17c-4d75-9085-a77c5f970e0a@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox