From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] dkms v3.0.6 does not create /var/lib/dkms which is needed to build dkms modules
Date: Sat, 03 Sep 2022 03:42:33 +0200 [thread overview]
Message-ID: <20220903014233.MxZ1o6KAmkiSloh8wA0IymPBQxxgHgI8LLlQZDgVLq0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39066@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Closed issue by tdm4 on void-packages repository
https://github.com/void-linux/void-packages/issues/39066
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64 GenuineIntel notuptodate rFFFF
### Package(s) Affected
dkms-3.0.6_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
When dkms is installed fresh with version 3.0.6_1 it's supposed to create a /var/lib/dkms directory which is required for building DKMS modules.
### Actual behaviour
/var/lib/dkms is not created when package is installed fresh.
See this pull request: https://github.com/void-linux/void-packages/commit/efe694ed366e77a281c6e4745bc7e14ff686af3b
srcpkgs/dkms/template line 28:
- vinstall dkms_dbversion 644 var/lib/dkms
(Line is removed -- this breaks a fresh install because it never creates /var/lib/dkms)
### Steps to reproduce
1. Fresh install of Void Linux
2. Install dkms
3. Try installing any -dkms package
4. DKMS fails to create the module
next prev parent reply other threads:[~2022-09-03 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 19:48 [ISSUE] " tdm4
2022-09-02 19:51 ` tdm4
2022-09-02 19:52 ` ahesford
2022-09-02 19:55 ` paper42
2022-09-03 1:42 ` ahesford [this message]
2022-09-03 1:46 ` ahesford
2022-09-03 17:58 ` subnut
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=20220903014233.MxZ1o6KAmkiSloh8wA0IymPBQxxgHgI8LLlQZDgVLq0@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).