On Mon, 2020-06-22 at 11:57 +0100, Alex Kiernan wrote: > Generate output for each contaminated path so it's visible in the main > log file, then enable rootfs_check_host_user_contaminated by default. > > Signed-off-by: Alex Kiernan <[email protected]> > --- > > Changes in v2: > - expose each contaminated path in the main log > > meta/classes/rootfs-postcommands.bbclass | 9 ++++----- > 1 file changed, 4 insertions(+), 5 deletions(-)
Thanks, this is definitely more helpful. Some warnings in the test build: https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/2046 step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs is owned by the same user or group as the user running bitbake: /var/lib/nfs/statd step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs is owned by the same user or group as the user running bitbake: /var/lib/nfs/statd/sm.bak step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs is owned by the same user or group as the user running bitbake: /var/lib/nfs/statd/state step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs is owned by the same user or group as the user running bitbake: /var/lib/nfs/statd/sm https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/2073 step3b: WARNING: core-image-sato-1.0-r0 do_rootfs: Path in the rootfs is owned by the same user or group as the user running bitbake: /var/cache/fontconfig/CACHEDIR.TAG which does raise more questions. Its conceivable its even related to the pseudo issue I just sent a patch for... Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139751): https://lists.openembedded.org/g/openembedded-core/message/139751 Mute This Topic: https://lists.openembedded.org/mt/75035700/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
