Re: [OE-Core][PATCH v2] rootfs-postcommands: Enable rootfs_check_host_user_contaminated

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

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 <alex.kiernan@gmail.com>
> ---
> 
> 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