public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: yi liu <liuyi@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Duplicated dtb files issue for multiple confiugrations
Date: Mon, 3 Jun 2024 05:46:22 -0700 (PDT)	[thread overview]
Message-ID: <c426ad86-5cc5-42e6-8223-e7a7e5b3424en@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1920 bytes --]

Hi all,

I am trying to make use of isar image installer to create the installer for 
some distro based on meta-iot2050 
(https://github.com/siemens/meta-iot2050). During the build process, I got 
error below:

|ERROR: mc:isar-installer:isar-image-installer-1.0-r0 do_copy_boot_files: 
The recipe isar-|image-installer is trying to install files into a shared 
area when those files already exist. |Those files and their manifest 
location are:
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-m2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-pg2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic-pg2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-sm.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|Please verify which recipe should provide the above files.

It looks like the isar image installer utilizes multiple configurations to 
build the installer image and the target image at the same time. After 
searching from the mail list, I found this issue has been reported in other 
threads with similar cases (building multiple images for the same machine):
- https://groups.google.com/g/isar-users/c/qAnjahjjfsw
- https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
- https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
- https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8

Is anyone still working on this issue? 

Best Regards,
Liu Yi

[-- Attachment #1.2: Type: text/html, Size: 2074 bytes --]

             reply	other threads:[~2024-06-03 12:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 12:46 yi liu [this message]
2024-06-04 12:38 ` Uladzimir Bely
2024-06-05 16:23   ` Jan Kiszka
2024-06-06  7:24   ` Yi Liu
2024-06-10 10:10     ` Baurzhan Ismagulov

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=c426ad86-5cc5-42e6-8223-e7a7e5b3424en@googlegroups.com \
    --to=liuyi@siemens.com \
    --cc=isar-users@googlegroups.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