Thanks Ross, Khem It looks like we aren’t setting ‘read-only-rootfs’
Our images and init are very customized, so we missed that. Will look into it. Regards, MV From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: November 09, 2016 08:19 To: Vuille, Martin (Martin) Cc: yocto@yoctoproject.org Subject: Re: [yocto] Postinsts question On 8 November 2016 at 23:23, Vuille, Martin (Martin) <vmar...@avaya.com<mailto:vmar...@avaya.com>> wrote: We are running with our rootfs mounted read-only. Consequently, any postinsts that get deferred to first boot fail. Is there a way to fail the build for any postinsts that can’t be performed during the build and have to be deferred? I was looking at some other selftests today and a test suggested that this already happens, and it's true. If you add 'read-only-rootfs' to IMAGE_FEATURES then delayed postists are fatal: ERROR: core-image-sato-base-1.0-r0 do_rootfs: The following packages could not be configured offline and rootfs is read-only: ['postinst-test-delayed'] ERROR: core-image-sato-base-1.0-r0 do_rootfs: Function failed: do_rootfs Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
