Re: [OE-core] [PATCH v3] bitbake.conf: pseudo to ignore vim and less config files

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Mon, May 05, 2025 at 02:29:57PM +0100, Richard Purdie wrote:
> On Mon, 2025-05-05 at 16:08 +0300, Mikko Rapeli via lists.openembedded.org wrote:
> > vim and less always write to these files in users home directory.
> > Using vim and less via pseudo in "bitbake -c devshell recipe" and
> > outside of pseudo triggers pseudo aborts which makes interactive
> > use of devshell difficult. Fixes vim and less crashes and related
> > pseudo log entries:
> > 
> > inode mismatch: '/home/builder/.viminfo' ino 33270730 in db, 33269736 in request.
> > inode mismatch: '/home/builder/.lesshst' ino 33270625 in db, 33270730 in request.
> > 
> > Ignoring all files with ${HOME}/. in path fails since tools seem
> > to be using these paths, e.g. trusted-firmware-a from meta-arm.
> > 
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> > �meta/conf/bitbake.conf | 2 ++
> > �1 file changed, 2 insertions(+)
> > 
> > v3: back to .less and .vim paths due to failures from trusted-firmware-a in meta-arm,
> > ��� added comment
> 
> What paths are they using exactly? That sounds odd...

With ${HOME}/. in ignored paths, I have a lot of recipes now installing non-root
owned files and failing qa checks. Sadly this propagated to sstate cache.
List of affected meta-arm recipes from small firmware builds:

trusted-firmware-a
ts-sp-block-storage
ts-sp-attestation
ts-sp-crypto
ts-sp-smm-gateway
ts-sp-storage
ts-sp-its

I tried PSEUDO_VERBOSE flags to figure out what is going on but that did
not help. I can try again if you have some hints on how to debug this
but it's clear that very bad things(tm) happen if ${HOME}/. is in pseudo
ignored paths. And I really don't want to dive into various broken
tools/toolchains just because I want less and vim to not crash inside
devshell all the time. Common things behind these recipes are
makefiles, CMake, dtc and custom python scripts.

Cheers,

-Mikko