From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 7376257954614345728
X-Received: by 2002:a05:6214:4348:b0:6af:6ec6:226f with SMTP id 6a1803df08f44-6af6ec626bdmr44359656d6.47.1717418887920;
        Mon, 03 Jun 2024 05:48:07 -0700 (PDT)
X-BeenThere: isar-users@googlegroups.com
Received: by 2002:a05:6214:d06:b0:6a0:f448:96ca with SMTP id
 6a1803df08f44-6ae0ba4ea7bls576136d6.0.-pod-prod-04-us; Mon, 03 Jun 2024
 05:48:07 -0700 (PDT)
X-Received: by 2002:a05:6214:1bc7:b0:6aa:ff38:8bae with SMTP id 6a1803df08f44-6aecd6ee30bmr3985136d6.9.1717418887450;
        Mon, 03 Jun 2024 05:48:07 -0700 (PDT)
Received: by 2002:a05:620a:6116:b0:790:efaf:f1f8 with SMTP id af79cd13be357-794eb21007bms85a;
        Mon, 3 Jun 2024 05:46:23 -0700 (PDT)
X-Google-Smtp-Source: AGHT+IGQaFhOLxTLWxE8A+C5KJg43TnIDS/JqDv2Vy82oYmnymxsqVw58ZXzhJslET82mCvea+qfWny0Tw==
X-Received: by 2002:a05:620a:45ab:b0:794:f28c:42f4 with SMTP id af79cd13be357-794f5ec8e3amr11793185a.15.1717418782329;
        Mon, 03 Jun 2024 05:46:22 -0700 (PDT)
X-Google-Thread-Subscription: Yes
X-Google-Web-Client: true
Date: Mon, 3 Jun 2024 05:46:22 -0700 (PDT)
From: yi liu <liuyi@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Message-Id: <c426ad86-5cc5-42e6-8223-e7a7e5b3424en@googlegroups.com>
Subject: Duplicated dtb files issue for multiple confiugrations
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_332226_1158909617.1717418782125"
X-TUID: 5HLrtdk4v0Ba

------=_Part_332226_1158909617.1717418782125
Content-Type: multipart/alternative; 
	boundary="----=_Part_332227_1110970945.1717418782125"

------=_Part_332227_1110970945.1717418782125
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

------=_Part_332227_1110970945.1717418782125
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all,<br /><br />I am trying to make use of isar image installer to creat=
e the installer for some distro based on meta-iot2050 (https://github.com/s=
iemens/meta-iot2050). During the build process, I got error below:<br /><br=
 />|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 locat=
ion are:<br />|=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-ad=
vanced-m2.dtb<br />|=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-ba=
se-dev.copy_boot_files)<br />|=C2=A0 /build/tmp/deploy/images/iot2050/k3-am=
6528-iot2050-basic.dtb<br />|=C2=A0 =C2=A0 (matched in manifest-arm64-img-j=
upiter-base-dev.copy_boot_files)<br />|=C2=A0 /build/tmp/deploy/images/iot2=
050/k3-am6548-iot2050-advanced-pg2.dtb<br />|=C2=A0 =C2=A0 (matched in mani=
fest-arm64-img-jupiter-base-dev.copy_boot_files)<br />|=C2=A0 /build/tmp/de=
ploy/images/iot2050/k3-am6528-iot2050-basic-pg2.dtb<br />|=C2=A0 =C2=A0 (ma=
tched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)<br />|=C2=A0 =
/build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced.dtb<br />|=C2=
=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)=
<br />|=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-s=
m.dtb<br />|=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.c=
opy_boot_files)<br />|Please verify which recipe should provide the above f=
iles.<br /><br />It looks like the isar image installer utilizes multiple c=
onfigurations 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 repo=
rted in other threads with similar cases (building multiple images for the =
same machine):<br />- https://groups.google.com/g/isar-users/c/qAnjahjjfsw<=
br />- https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA<br />- https://=
groups.google.com/g/isar-users/c/ZMD4XY4dKWQ<br />- https://groups.google.c=
om/g/isar-users/c/PSGU_AcdPZ8<br /><br />Is anyone still working on this is=
sue? <br /><br />Best Regards,<br />Liu Yi<br />
------=_Part_332227_1110970945.1717418782125--

------=_Part_332226_1158909617.1717418782125--