From: MaMiMa81 <MaMiMa81@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "depmod: WARNING" after kmod update
Date: Fri, 12 Aug 2022 16:45:44 +0200 [thread overview]
Message-ID: <20220812144544.k3SFwrRrpTiq_2Jd3-n3_K5S5K7g85Groj8jAZbseT4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38367@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]
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 - espescially 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.
next prev parent reply other threads:[~2022-08-12 14:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 10:20 [ISSUE] " Haagen-Dazs
2022-07-30 13:36 ` Haagen-Dazs
2022-08-05 17:52 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-07 2:13 ` Haagen-Dazs
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:58 ` TeusLollo
2022-08-07 20:51 ` Haagen-Dazs
2022-08-08 1:34 ` ahesford
2022-08-08 9:12 ` TeusLollo
2022-08-12 13:29 ` MaMiMa81
2022-08-12 13:30 ` MaMiMa81
2022-08-12 13:34 ` MaMiMa81
2022-08-12 14:45 ` MaMiMa81 [this message]
2022-08-12 14:56 ` MaMiMa81
2022-08-12 16:24 ` TeusLollo
2022-08-17 17:13 ` MaMiMa81
2022-08-17 17:15 ` MaMiMa81
2022-08-17 17:23 ` MaMiMa81
2022-08-17 17:25 ` MaMiMa81
2022-08-17 17:26 ` MaMiMa81
2022-08-17 17:29 ` ahesford
2022-08-17 19:59 ` TeusLollo
2022-08-17 20:00 ` TeusLollo
2022-08-18 15:12 ` MaMiMa81
2022-08-22 15:22 ` TeusLollo
2022-08-23 15:49 ` [ISSUE] [CLOSED] " ahesford
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=20220812144544.k3SFwrRrpTiq_2Jd3-n3_K5S5K7g85Groj8jAZbseT4@z \
--to=mamima81@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).