| Message ID | 20230201142946.25192-1-venkata.pyla@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | [isar-cip-core] kas/opt/swupdate.yml: Add tar.gz for reproducible build checks | expand |
On 01.02.23 15:29, venkata.pyla@toshiba-tsip.com wrote: > From: venkata pyla <venkata.pyla@toshiba-tsip.com> > No reasoning given. > Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com> > --- > kas/opt/swupdate.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kas/opt/swupdate.yml b/kas/opt/swupdate.yml > index f0d3f1b..7941769 100644 > --- a/kas/opt/swupdate.yml > +++ b/kas/opt/swupdate.yml > @@ -21,7 +21,7 @@ local_conf_header: > wic-swu: | > IMAGE_CLASSES += "squashfs" > IMAGE_TYPEDEP_wic += "squashfs" > - IMAGE_FSTYPES = "wic" > + IMAGE_FSTYPES = "wic tar.gz" This makes no sense for the original purpose: Building an swupdate image. At least to my understanding, that tar.gz will solely consist of the rootfs content, can't be used for anything related to swupdate. Jan > WKS_FILE ?= "${MACHINE}-${SWUPDATE_BOOTLOADER}.wks.in" > INITRAMFS_INSTALL_append = " initramfs-squashfs-hook" > WIC_DEPLOY_PARTITIONS = "1"
diff --git a/kas/opt/swupdate.yml b/kas/opt/swupdate.yml index f0d3f1b..7941769 100644 --- a/kas/opt/swupdate.yml +++ b/kas/opt/swupdate.yml @@ -21,7 +21,7 @@ local_conf_header: wic-swu: | IMAGE_CLASSES += "squashfs" IMAGE_TYPEDEP_wic += "squashfs" - IMAGE_FSTYPES = "wic" + IMAGE_FSTYPES = "wic tar.gz" WKS_FILE ?= "${MACHINE}-${SWUPDATE_BOOTLOADER}.wks.in" INITRAMFS_INSTALL_append = " initramfs-squashfs-hook" WIC_DEPLOY_PARTITIONS = "1"