New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
Regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - especially as it appears that it is moving to be more systemd centric - plus this will also put more demand upon core devs, would not a simple & sensible course of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely put it forward as a suggestion to try and help.

Also regarding @ahesford:

>     3. ........ (Documenting that this causes a real problem beyond spitting out some warnings will almost certainly increase the sense of urgency there.)


See here:

[https://groups.google.com/g/linux.debian.bugs.dist/c/7hZiQYDXaiI](url)


#Michael Biebl
unread,
Jul 7, 2022, 11:40:03 AM
to

Control: severity -1 important

On Mon, 04 Jul 2022 15:01:13 +1000 Konomi Kitten
<konomi...@gmail.com> wrote:
> Package: initramfs-tools
> Version: 0.141
> Severity: minor
> X-Debbugs-Cc: konomi...@gmail.com
>
> When update-initramfs runs I receive the following message:
>
> depmod: WARNING: could not open modules.builtin.modinfo at
> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> directory


Unfortunately this is not a minor issue, as it breaks the autopkgtest
suite of initramfs-tools and thus prevents kmod from entering testing
(and dependent packages like systemd [1] as well).

It would thus be great to have the patch in [2] applied and uploaded
soon. I can offer to NMU if available time is an issue.

Regards,
Michael 


So it is probably of some importance that this is attended to.
Incidently I have currently downgraded to kmod v.29 as alluded to in that linked bug report.