From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v7 3/3] meta: Deploy image build artifacts into distro- and image-specific subdirs
Date: Fri, 10 Apr 2026 09:44:04 +0000 [thread overview]
Message-ID: <c576aebcf2cefe7db948970178cd1e515c072011.camel@siemens.com> (raw)
In-Reply-To: <20260226162613.1954014-4-wzh@ilbers.de>
On Thu, 2026-02-26 at 17:26 +0100, Zhihang Wei wrote:
> From: Ilia Skochilov <iskochilov@ilbers.de>
>
> When building different distros or images for the same machine (e.g.
> phyboard-mira-bullseye and phyboard-mira-bookworm, or isar-image-ci
> and isar-image-base), artifacts with identical names (e.g. DTB files)
> may be deployed to the same location, resulting file conflicts and
> build failures.
>
> Deploy image build artifacts into a subdirectory named
> ${DISTRO}-${IMAGE_PN} to avoid such collisions.
>
> Since the directory now encodes the distro and image name, remove the
> ${DISTRO} and ${IMAGE_PN} prefixes from artifact filenames to
> keep the names short and clear.
>
[shortening a bit]
>
> +IMAGE_PN ?= ""
> +DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}${@('/%s-%s' % (d.getVar('DISTRO'), d.getVar('IMAGE_PN'))) if d.getVar('IMAGE_PN') != '' else ''}"
This cannot work, as the value of IMAGE_PN is late-expanded, hence
different in the initrd recipe and the image recipe. The
DEPLOY_DIR_IMAGE variable must only use data that is machine specific,
not image specific (distro might be fine, though as this is identical
for both initrd and image).
Voting for a revert of this patchset.
PS: Regarding the DTB issue? Can't we simply prefix the DTBs with the
IMAGE_PN? In do_copy_boot_files we know the IMAGE_PN and during wic-
imaging we can remove the prefix again.
Best regards,
Felix
--
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/c576aebcf2cefe7db948970178cd1e515c072011.camel%40siemens.com.
next prev parent reply other threads:[~2026-04-10 9:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:26 Deploy DTBs and other image artifacts into subdirs to avoid conflicts Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 1/3] wic: Obtain real machine name in isoimage source plugin Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 2/3] testsuite: Add testcases to check dtb deployment Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 3/3] meta: Deploy image build artifacts into distro- and image-specific subdirs Zhihang Wei
2026-03-02 9:45 ` 'Jan Kiszka' via isar-users
2026-03-03 10:22 ` Zhihang Wei
2026-03-03 12:50 ` 'Jan Kiszka' via isar-users
2026-03-03 13:35 ` Zhihang Wei
2026-03-24 14:36 ` Zhihang Wei
2026-03-24 14:48 ` 'Jan Kiszka' via isar-users
2026-03-25 16:41 ` Baurzhan Ismagulov
2026-03-26 6:03 ` 'Jan Kiszka' via isar-users
2026-03-26 15:56 ` Baurzhan Ismagulov
2026-03-27 6:33 ` 'Jan Kiszka' via isar-users
2026-04-10 9:44 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-04-10 10:35 ` 'Jan Kiszka' via isar-users
2026-04-10 10:46 ` Zhihang Wei
2026-04-10 11:39 ` 'MOESSBAUER, Felix' via isar-users
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=c576aebcf2cefe7db948970178cd1e515c072011.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@ilbers.de \
/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