On Monday, August 31, 2020 at 7:33:16 PM UTC+5:30 Jan Kiszka wrote: > On 24.08.20 11:27, Vijai Kumar K wrote: > > The following series updates the wic to the latest one from > > openembedded core. The git tree is available here. > > > > https://github.com/vj-kumar/isar/tree/wic/staging0 > > > > Below are summary of key changes in the below series. > > > > P3 & P6: > > The latest version of WIC detects the presence of fakeroot using > > pseudo_dir(${IMAGE_ROOTFS}/../pseudo). If this is non-existent it > doesnot > > use fakeroot. P3 handles that quirk. There is also a standalone > invocation of > > pseudo which P6 tries to handle via wic_fakeroot. > > > > In case of ISAR, we need wic_fakeroot as fakeroot only for 2 purposes. > > 1. To workaround fsck return values for stretch > > 2. To handle standalone invocation of pseudo(P4 in series) > > > > Number 2 is not needed if we dont use fakeroot. > > > > The alternative approach to fakeroot is to carry patches on top of wic > > directory instead of working around such quirks using fakeroot. The > downside > > being the need to rebase the local changes on future updates of wic. > > > > > > P4 & P5: > > These cherry-picked changes address the --exclude-path issues which > Henning > > has addressed in [2]. Should be dropped once that is merged. > > > > P9: > > P9 is needed for --include-path to work. I have observed that > --include-path > > does not yet work/broken in the latest OE-core/poky. Posted a query in > [1]. In ISAR > > it works with P9 fix. P9 fix could also be relevant upstream and can be > sent there > > for review. > > > > Apart from the normal qemu build test, Below are the list of features > tested. > > KS API: > > --exclude-path > > --include-path > > --fsuuid > > --overhead-factor > > --fixed-size > > --use-label > > --use-uuid > > > > Standalone invocations: > > wic ls > > wic cp > > wic rm > > > > Currently in the process of finding a way to test wic features > automatically. Some wic features > > like -fsuuid cannot be validated till we boot the target. Need to find a > generalized way for > > testing the available wic features. The approach in hand is to use a > wic-test.wks file and > > generate qemu image with that to validate the wic features. > > > > [1] https://lists.yoctoproject.org/g/poky/message/12151 > > [2] https://groups.google.com/g/isar-users/c/xePCyEl2qhM/m/mwFdeou0AQAJ > > > > FWIW, I've tested a couple of images built by jailhouse-images, and no > issues so far. > > Jan > Thank you Jan. Also, I have tested the wic with jailhouse-images & isar-siemens project. No issues were found. https://github.com/vj-kumar/jailhouse-images/commits/wic/update + https://github.com/vj-kumar/isar/commits/wic/staging1 Best, Vijai Kumar K > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux >