| 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: | 160 |
| Popularity: | 1.50 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2024-03-13 08:43 (UTC) |
iusrlinearb,
Doesn't appear to build, at least on my system.
==> Verifying source file signatures with gpg...
zfs-0.8.3.tar.gz ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!
...
This package doesn't support people who have failed to read the wiki page https://wiki.archlinux.org/index.php/Makepkg, or cannot interpret error messages.
I'm using zfs-dkms on x86_64 5.4.25-2-lts is it normal to see the following in boot logs?
mars 16 07:04:09 smicro kernel: zlua: loading out-of-tree module taints kernel.
mars 16 07:04:09 smicro kernel: zlua: module license 'MIT' taints kernel.
mars 16 07:04:09 smicro kernel: Disabling lock debugging due to kernel taint
mars 16 07:04:09 smicro kernel: zlua: module verification failed: signature and/or required key missing - tainting kernel
Great idea adding the 5.5 patch. Now that ZFS fixed SIMD support I upgraded for the first time in over a year from kernel 4.19 and it was painless. Thank you.
@sphere101: went from 5.4.15-arch1-1 to the latest today (5.5.7.arch1-1) and it built just fine.
Has anyone tested this latest zfs-dkms 0.8.3-2 with the 5.5.X kernel and latest gcc? If so, what is the process? Upgrade zfs-dkms and zfs-utils followed by a system update pacman -Syyu? Thank you.
@mikeyyve: compiles. The filesystem is mountable
Anyone tried kernel 5.5 with the changes eschwartz uploaded?
Upstream landed a patch that is supposed to fix compilation on kernel 5.5, which I am in the process of cherry-picking.
EDIT: uploaded
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)