Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "depmod: WARNING" after kmod update
Date: Mon, 08 Aug 2022 03:34:28 +0200	[thread overview]
Message-ID: <20220808013428.Z2N-_es8f26fwy4FQP3zo1sEONa0HOU4my_vXw_5HPU@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: 1273 bytes --]

New comment by ahesford on void-packages repository

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

Comment:
1. `mkinitcpio` is an Arch project and works fine with Void as is. I personally use `mkinitcpio` on most of my systems, even as the foundation of my ZFSBootMenu images, and have a vested interest in making sure it stays that way. But there's no need to attempt to take ownership over from Arch.
2. Has anybody shown that this warning actually indicates a problem with the initramfs image? It says "WARNING" right in the text, and even before I pulled the `mkinitcpio` patch from upstream, I confirmed that expected kernel modules made their way into initramfs images.
3. Somebody is welcome to PR a backport of the fix to our current dracut pending a full update. (It won't be me because I no longer have installations that will let me meaningfully test the patch.) Otherwise, as I noted when closing an untested PR to bump the dracut package, a full update requires more extensive testing and will hopefully be done once a core member finds some time and interest to take up the matter. (Documenting that this causes a real problem beyond spitting out some warnings will almost certainly increase the sense of urgency there.)

  parent reply	other threads:[~2022-08-08  1:34 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 [this message]
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
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=20220808013428.Z2N-_es8f26fwy4FQP3zo1sEONa0HOU4my_vXw_5HPU@z \
    --to=ahesford@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).