From: "Yoann Congal" <yoann.congal@smile.fr>
To: <abiswas@lynx.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "Harish Bansal" <hbansal@lynx.com>
Subject: Re: [OE-core] Walnascar: enquiry about backporting the pseudo openat2 fix
Date: Tue, 13 Oct 2026 08:54:30 +0200 [thread overview]
Message-ID: <DM3IHJS5SOAY.3RZ32LVIU57KO@smile.fr> (raw)
In-Reply-To: <CH2PR22MB2038668BD49A629158C12893CA9E2@CH2PR22MB2038.namprd22.prod.outlook.com>
On Tue Oct 13, 2026 at 7:15 AM CEST, Ansh Biswas via lists.openembedded.org wrote:
> Hi,
Hello,
> We encountered a linux-libc-headers failure on Walnascar during tar
> extraction, with errors including “unknown base path for fd” and
> “Cannot mkdir: Bad address”.
> Updating pseudo to SRCREV 9ab513512d8b5180a430ae4fa738cb531154cdef
> resolved the observed failure in our tests. The forced packaging task
> was completed successfully on Ubuntu 22.04 with GNU tar 1.34 and
> Ubuntu 24.04 with GNU tar 1.35, using BitBake 2.12.1.
> This pseudo revision is already included in OE-Core master through
> commit 2c20c05b324e5d6564c8554381019170839509bb.
> I understand Walnascar is EOL and backports are normally not accepted.
> Would you consider a backport for this issue, or should we maintain it
> downstream?
Sorry but no, I won't consider it.
Walnascar is EOL and the situation you describe does not fall into the
very (very!) rare cases where we would backport commits to EOL branches.
You will have to maintain it downstream.
Obviously, I recommend an upgrade to a maintained branch.
Regards,
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-10-13 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 5:15 Walnascar: enquiry about backporting the pseudo openat2 fix Ansh Biswas
2026-10-13 6:54 ` Yoann Congal [this message]
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=DM3IHJS5SOAY.3RZ32LVIU57KO@smile.fr \
--to=yoann.congal@smile.fr \
--cc=abiswas@lynx.com \
--cc=hbansal@lynx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox