From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mikko.rapeli@linaro.org, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3] bitbake.conf: pseudo to ignore vim and less config files
Date: Mon, 05 May 2025 14:29:57 +0100 [thread overview]
Message-ID: <dddfbb46a17195fde3ff7cb5667c84a9b68235bc.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250505130830.995042-1-mikko.rapeli@linaro.org>
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...
Cheers,
Richard
next prev parent reply other threads:[~2025-05-05 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 13:08 [PATCH v3] bitbake.conf: pseudo to ignore vim and less config files Mikko Rapeli
2025-05-05 13:29 ` Richard Purdie [this message]
2025-05-05 13:47 ` [OE-core] " Mikko Rapeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dddfbb46a17195fde3ff7cb5667c84a9b68235bc.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.