From: Haagen-Dazs <Haagen-Dazs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "depmod: WARNING" after kmod update
Date: Sun, 07 Aug 2022 04:13:12 +0200 [thread overview]
Message-ID: <20220807021312.NjBJmCCpfX4GmFkt-b_QgZIY0GNMnJpThG7jJG2Lk1c@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: 457 bytes --]
New comment by Haagen-Dazs on void-packages repository
https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207315757
Comment:
> This output was generated circa 24 hours ago. Feel free to delete this if it's not relevant anymore
It is still relevant, dracut is still not patched for the kmod update.
[mkinitcpio](https://github.com/void-linux/void-packages/commit/ff39c912d412717d17232de9564f659b037e95b5) is already patched though.
next prev parent reply other threads:[~2022-08-07 2:13 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 [this message]
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
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=20220807021312.NjBJmCCpfX4GmFkt-b_QgZIY0GNMnJpThG7jJG2Lk1c@z \
--to=haagen-dazs@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).