Fixed, hunted down and grabbed commits from master instead.
Search Criteria
Package Details: zfs-dkms 2.2.4-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
|---|---|
| Package Base: | zfs-dkms |
| Description: | Kernel modules for the Zettabyte File System. |
| Upstream URL: | https://zfsonlinux.org/ |
| Licenses: | CDDL |
| Provides: | SPL-MODULE, zfs, ZFS-MODULE |
| Submitter: | isiachi |
| Maintainer: | kstolp |
| Last Packager: | kstolp |
| Votes: | 162 |
| Popularity: | 3.15 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2024-05-03 03:00 (UTC) |
Dependencies (2)
- dkms
- zfs-utilsAUR (zfs-linux-gitAUR, zfs-utils-gitAUR, zfs-utils-staging-gitAUR)
Required by (19)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (4)
eschwartz commented on 2019-09-24 11:43 (UTC)
freswa commented on 2019-09-24 11:28 (UTC) (edited on 2019-09-24 11:28 (UTC) by freswa)
Tonyhutter rebased his PR branch so the Github links don't work anymore. Maybe we better include them in our repo.
2G_Storm commented on 2019-09-24 08:21 (UTC) (edited on 2019-09-24 08:24 (UTC) by 2G_Storm)
Does it still break with 5.3 kernel?
bone commented on 2019-09-24 07:37 (UTC) (edited on 2019-09-24 07:42 (UTC) by bone)
I get an error during make: https://pastebin.com/D4hBXPeK
"The requested URL returned error: 406 Not Acceptable."
Timezone is CEST. Anyone else with this problem? (or is it on my side?)
eschwartz commented on 2019-09-20 18:29 (UTC)
Subscribed to the zfsonlinux issue -- any update on getting that merged any time soon???
There are four patches on that list marked as "Linux 5.3 compat", so if an 0.8.2 release does not look imminent we can try backporting those, which should hopefully be enough.
fryfrog commented on 2019-09-20 18:21 (UTC)
And the future 0.8.2 release looks like it should solve it.
vk77de commented on 2019-09-20 18:19 (UTC)
linux 5.3.arch1-1 breaks ZFS
https://bugs.archlinux.org/task/63864 https://github.com/zfsonlinux/zfs/issues/9332
patrickh commented on 2019-08-11 11:02 (UTC) (edited on 2019-08-11 11:05 (UTC) by patrickh)
@edacval thanks for the link! Already did my research a few days ago and did not check before posting, sorry … :)
edacval commented on 2019-08-11 09:56 (UTC)
@patrickh : https://github.com/zfsonlinux/zfs/issues/9133
patrickh commented on 2019-08-11 07:48 (UTC) (edited on 2019-08-11 07:49 (UTC) by patrickh)
I just wanted to ask, if anyone had the luck to get this working together with linux-mainline kernel (version 5.3-rc3 or other rc versions)? I would like to try new hardware, that will be supported in 5.3 only, therefore I am trying things out.
I know that this is probably not yet officially supported, but I was wondering, if the build errors that I see are a result of missing support for 5.3 on the ZFS side for now, or if it is just that the dkms build process is not compatible with the linux-mainline package here in general?
Here is my /var/lib/dkms/zfs/git/build/make.log:
https://gist.github.com/c529e36107dc0f93a04b7e4c5612f24b ¹
Maybe someone who understands the dkms build process better than me could give me a hint, if it makes sense to report this to upstream or if I should just wait for official 5.3 release of core/linux package?
Thanks and best regards!
¹ sorry for the German "Notice" messages in the log. I changed my LC_ALL, but it didn't seem to work. But as far as I understand, the real issue is right at the end here:
make[2]: *** No rule to make target 'module/Module.symvers', needed by 'all-am'. Stop.
Pinned Comments
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)