From: Adolf Belka <adolf.belka@ipfire.org>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>,
Michael Tremer <michael.tremer@ipfire.org>
Subject: Re: dracut-ng fix for glibc 2.44 fts regression — LoongArch build
Date: Mon, 26 Oct 2026 11:15:38 +0100 [thread overview]
Message-ID: <3a2c9527-c28f-4496-a067-a9b61a247c2d@ipfire.org> (raw)
In-Reply-To: <c3d60ab-a8d-13b7-4231-aa4a1bee82ed@gmail.com>
Hi Vincent,
I think the best thing is to implement the updated dracut. I had missed the updates of this package and I note that dracut-ng-112 includes security fixes.
So I will issue an update for it and also add it to my nvchecker list so I get informed when new versions are issued.
Regards,
Adolf.
On 26/10/2026 03:47, Vincent Li wrote:
>
> Hi Michael,
>
> Sorry, I deleted the email about the potential glibc 2.44 regression https://sourceware.org/bugzilla/show_bug.cgi?id=34861, so I'm starting a new thread.
>
> From https://sourceware.org/bugzilla/show_bug.cgi?id=34078, I confirmed that my LoongArch build environment needs the fix from https://github.com/dracut-ng/dracut-ng/pull/2394 to work around the glibc 2.44 issue. dracut-ng 112 already includes the fix.
>
> Do you think it's a good idea to carry the dracut-ng fix in the IPFire build for LoongArch, even though the IPFire build environment doesn't currently experience this issue?
>
> Best,
> Vincent
next prev parent reply other threads:[~2026-10-26 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 2:47 Vincent Li
2026-10-26 10:15 ` Adolf Belka [this message]
2026-10-26 23:38 ` Vincent Li
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=3a2c9527-c28f-4496-a067-a9b61a247c2d@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.org \
--cc=vincent.mc.li@gmail.com \
/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