Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] problems with zfs-0.8.3_2
@ 2020-04-05 16:02 emacsomancer
  2020-04-05 16:04 ` xtraeme
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-05 16:02 UTC (permalink / raw)
  To: ml

[-- 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`


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
@ 2020-04-05 16:04 ` xtraeme
  2020-04-05 16:09 ` emacsomancer
                   ` (6 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: xtraeme @ 2020-04-05 16:04 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 155 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609439830

Comment:
Killed rofl 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
  2020-04-05 16:04 ` xtraeme
@ 2020-04-05 16:09 ` emacsomancer
  2020-04-05 16:09 ` emacsomancer
                   ` (5 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-05 16:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

New comment by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609440611

Comment:
> Killed rofl

It wasn't killed via user input, either the first time this occurred via `sudo xbps-install -Su` or via `sudo xbps-reconfigure -f linux4.14`.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
  2020-04-05 16:04 ` xtraeme
  2020-04-05 16:09 ` emacsomancer
@ 2020-04-05 16:09 ` emacsomancer
  2020-04-05 16:09 ` emacsomancer
                   ` (4 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-05 16:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 340 bytes --]

New comment by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609440611

Comment:
> Killed rofl

It wasn't killed via user input, either the first time this occurred via `sudo xbps-install -Su` or the second time when it occurredd via `sudo xbps-reconfigure -f linux4.14`.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
                   ` (2 preceding siblings ...)
  2020-04-05 16:09 ` emacsomancer
@ 2020-04-05 16:09 ` emacsomancer
  2020-04-05 21:26 ` ahesford
                   ` (3 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-05 16:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

New comment by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609440611

Comment:
> Killed rofl

It wasn't killed via user input, either the first time this occurred via `sudo xbps-install -Su` or the second time when it occurred via `sudo xbps-reconfigure -f linux4.14`.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
                   ` (3 preceding siblings ...)
  2020-04-05 16:09 ` emacsomancer
@ 2020-04-05 21:26 ` ahesford
  2020-04-05 22:09 ` ahesford
                   ` (2 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: ahesford @ 2020-04-05 21:26 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609486705

Comment:
The `zfs-0.8.3_2` DKMS builds for me with `linux4.14-414.174_1` on x86_64. Your text references `linux4.14`, but your output refers to `linux4.19`. I've had no problems building against either. Can you reconcile the difference and see if there is a DKMS build log in `/var/lib/dkms/zfs/0.8.3/build/make.log` that explains the error?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
                   ` (4 preceding siblings ...)
  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
  7 siblings, 0 replies; 9+ messages in thread
From: ahesford @ 2020-04-05 22:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609486705

Comment:
The `zfs-0.8.3_2` DKMS builds for me with `linux4.14-4.14.174_1` on x86_64. Your text references `linux4.14`, but your output refers to `linux4.19`. I've had no problems building against either. Can you reconcile the difference and see if there is a DKMS build log in `/var/lib/dkms/zfs/0.8.3/build/make.log` that explains the error?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
                   ` (5 preceding siblings ...)
  2020-04-05 22:09 ` ahesford
@ 2020-04-06  2:13 ` emacsomancer
  2020-04-06  2:13 ` [ISSUE] [CLOSED] " emacsomancer
  7 siblings, 0 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-06  2:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

New comment by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/issues/20673#issuecomment-609531183

Comment:
> The `zfs-0.8.3_2` DKMS builds for me with `linux4.14-4.14.174_1` on x86_64. Your text references `linux4.14`, but your output refers to `linux4.19`. I've had no problems building against either. Can you reconcile the difference and see if there is a DKMS build log in `/var/lib/dkms/zfs/0.8.3/build/make.log` that explains the error?

I was eventually able to get them to build, and so I didn't see anything in the DKMS build log after that. I'll keep an eye on it and re-open if I have something definitive.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [ISSUE] [CLOSED] problems with zfs-0.8.3_2
  2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
                   ` (6 preceding siblings ...)
  2020-04-06  2:13 ` emacsomancer
@ 2020-04-06  2:13 ` emacsomancer
  7 siblings, 0 replies; 9+ messages in thread
From: emacsomancer @ 2020-04-06  2:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

Closed 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`


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2020-04-06  2:13 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-05 16:02 [ISSUE] problems with zfs-0.8.3_2 emacsomancer
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

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).