From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] The DKMS kernel hook fails completely if a single module fails
Date: Sat, 11 Jul 2020 04:24:06 +0200 [thread overview]
Message-ID: <20200711022406.t5oAlEEKIA7hqUzwIPTwRROA1umXYZTwtxyAjpb6mJA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23124@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Closed issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/23124
Description:
### Expected behavior
If a DKMS module fails to build, all other modules should still be built.
### Actual behavior
If a DKMS module (such as NVIDIA for `linux5.7`) fails to build, it aborts the whole operation, skipping the attempt to build other modules, such as ZFS.
### Steps to reproduce the behavior
Have `linux5.7`, `linux5.7-headers`, `nvidia-dkms` and `zfs` installed. Try to run
```
# xbps-reconfigure -f linux5.7
linux5.7: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: nvidia-440.82.
Available DKMS module: zfs-0.8.4.
Building DKMS module: nvidia-440.82... FAILED!
Executing post-install kernel hook: 20-dracut ...
Executing post-install kernel hook: 20-dracut-uefi ...
Executing post-install kernel hook: 40-sbsigntool ...
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-gummiboot ...
Executing post-install kernel hook: 50-refind ...
linux5.7: configured successfully.
```
parent reply other threads:[~2020-07-11 2:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23124@inbox.vuxu.org>]
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=20200711022406.t5oAlEEKIA7hqUzwIPTwRROA1umXYZTwtxyAjpb6mJA@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).