On Fri, 3 Jan 2025 at 17:04, Helmut Grohne <helmut@subdivi.de> wrote:

On Fri, Jan 03, 2025 at 03:45:54PM +0000, Luca Boccassi wrote:

TL;DR: I have just spent some time to reproduce this with official
debian images and cannot reproduce this, hence closing as unactionable.

I think you missed the initial mail of this bug. The relevant code path
is not invoked when running initramfs-tools, but when using dracut. It's reproducible there. It also is reproducible in containers spawned from systemd-nspawn.

The official Debian initrd system is initramfs-tools, not dracut. If
you want to experiment with unsupported alternatives such as dracut
that's fine, but that's certainly not a "severity: serious" bug. Same
for nspawn, the official chroot tool in Debian is sbuild, you can
experiment with nspawn if you like, but if you want a supported tool
please use sbuild. If you want to use dracut, I suggest switching to
Fedora.

Given this alleged issue cannot be reproduced, given the proposed patch
is obviously wrong and has been rejected by all upstream maintainers as
it breaks other distros and there's no chance it will ever go anywhere,
and there's hence nothing really to be done, closing this bug.

You are saying that you closed the upstream MR, not someone else. You
further allege breakage of other distributions that could not be
practically validated.

No, as it can be plainly seen it was rejected by 3 maintainers out of
3, as it's clearly wrong.

Note that systemd's CI passed on the MR.

There is no validation for such use cases in the CI, so that doesn't
really mean anything.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)