From: Haagen-Dazs <Haagen-Dazs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] "depmod: WARNING" after kmod update
Date: Sat, 30 Jul 2022 12:20:18 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38367@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
New issue by Haagen-Dazs on void-packages repository
https://github.com/void-linux/void-packages/issues/38367
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.14_1 x86_64 AuthenticAMD uptodate FFF
### Package(s) Affected
kmod-30_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://groups.google.com/g/linux.debian.bugs.dist/c/7hZiQYDXaiI
### Expected behaviour
No errors given after `sudo xbps-reconfigure -fa`
### Actual behaviour
depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.../initramfs/lib/modules/5.18.14_1: No such file or directory
### Steps to reproduce
`sudo xbps-install -Su`
`sudo xbps-reconfigure -fa`
next reply other threads:[~2022-07-30 10:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 10:20 Haagen-Dazs [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38367@inbox.vuxu.org \
--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).