* Walnascar: enquiry about backporting the pseudo openat2 fix
@ 2026-10-13 5:15 Ansh Biswas
2026-10-13 6:54 ` [OE-core] " Yoann Congal
0 siblings, 1 reply; 2+ messages in thread
From: Ansh Biswas @ 2026-10-13 5:15 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org; +Cc: Harish Bansal
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
Hi,
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?
Thanks,
Ansh
[-- Attachment #2: Type: text/html, Size: 2385 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [OE-core] Walnascar: enquiry about backporting the pseudo openat2 fix
2026-10-13 5:15 Walnascar: enquiry about backporting the pseudo openat2 fix Ansh Biswas
@ 2026-10-13 6:54 ` Yoann Congal
0 siblings, 0 replies; 2+ messages in thread
From: Yoann Congal @ 2026-10-13 6:54 UTC (permalink / raw)
To: abiswas, openembedded-core@lists.openembedded.org; +Cc: Harish Bansal
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-10-13 6:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-13 5:15 Walnascar: enquiry about backporting the pseudo openat2 fix Ansh Biswas
2026-10-13 6:54 ` [OE-core] " Yoann Congal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox