From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com, jan.kiszka@siemens.com
Subject: Re: [PATCH v3 2/3] deploy boot files via sstate-cache
Date: Fri, 29 Dec 2023 09:29:19 +0200 [thread overview]
Message-ID: <ca1c878c-f865-49b9-8636-9b1e4957df62@ilbers.de> (raw)
In-Reply-To: <20230223064359.4171845-3-felix.moessbauer@siemens.com>
23/02/2023 08:43, Felix Moessbauer wrote:
> This patch changes how we deploy the boot files.
> Instead of manually deploying, we use the sstate infrastructure for
> that. By that, accidental overrides of the artifacts can be
> automatically detected. On clean, the artifacts are also cleaned.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
Hello Felix,
This logic fails on fargets that deploy DTB files if building several
distros
inside one builddir. DTB filenames are usually the same in this case, so
it is
detected as copy of already exist files.
Steps to reproduce:
$ bitbake mc:imx6-sabrelite-bullseye:isar-image-base
And right after then
$ bitbake mc:imx6-sabrelite-buster:isar-image-base
Will trigger:
ERROR: mc:imx6-sabrelite-buster:isar-image-base-1.0-r0 do_copy_boot_files:
The recipe isar-image-base is trying to install files into a shared area
when those files already exist.
next prev parent reply other threads:[~2023-12-29 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 6:43 [PATCH v3 0/3] Fix data-race in deployment of initrd Felix Moessbauer
2023-02-23 6:43 ` [PATCH v3 1/3] add initramfs to sstate-cache Felix Moessbauer
2023-02-23 6:43 ` [PATCH v3 2/3] deploy boot files via sstate-cache Felix Moessbauer
2023-12-29 7:29 ` Anton Mikanovich [this message]
2024-01-09 12:46 ` MOESSBAUER, Felix
2024-01-09 13:46 ` Jan Kiszka
2024-01-09 14:04 ` Anton Mikanovich
2024-01-10 4:27 ` Jan Kiszka
2024-02-26 13:32 ` Uladzimir Bely
2024-02-26 18:17 ` MOESSBAUER, Felix
2023-02-23 6:43 ` [PATCH v3 3/3] fix race-cond between default and custom initrd Felix Moessbauer
2023-03-06 6:05 ` [PATCH v3 0/3] Fix data-race in deployment of initrd Uladzimir Bely
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=ca1c878c-f865-49b9-8636-9b1e4957df62@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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