From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] problems with zfs-0.8.3_2
Date: Sun, 05 Apr 2020 18:02:31 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20673@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
New issue by emacsomancer on void-packages repository
https://github.com/void-linux/void-packages/issues/20673
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Linux sushoma 5.4.29_1 #1 SMP PREEMPT Wed Apr 1 10:52:40 UTC 2020 x86_64 GNU/Linux
* package:
zfs-0.8.3_2, linux4.14
### Expected behavior
Properly rebuild dkms modules.
### Actual behavior
Dies while building DKMS module. Even worse, this means it doesn't try to rebuild DKMS modules for other kernels (ideally a DKMS module dying in some fashion shouldn't stop the other modules from building...especially since all of the old ZFS DKMS modules get removed first)
```
sudo xbps-reconfigure -f linux4.19 linux5.4
linux4.19: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: acpi_call-1.2.0.
Available DKMS module: wireguard-1.0.20200401.
Available DKMS module: zfs-0.8.3.
Building DKMS module: acpi_call-1.2.0... done.
Building DKMS module: wireguard-1.0.20200401... done.
Building DKMS module: zfs-0.8.3... killed
```
### Steps to reproduce the behavior
Install new `zfs-0.8.3_2` or reconfigure `linux4.14`
next reply other threads:[~2020-04-05 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 16:02 emacsomancer [this message]
2020-04-05 16:04 ` xtraeme
2020-04-05 16:09 ` emacsomancer
2020-04-05 16:09 ` emacsomancer
2020-04-05 16:09 ` emacsomancer
2020-04-05 21:26 ` ahesford
2020-04-05 22:09 ` ahesford
2020-04-06 2:13 ` emacsomancer
2020-04-06 2:13 ` [ISSUE] [CLOSED] " emacsomancer
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-20673@inbox.vuxu.org \
--to=emacsomancer@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).