| 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: | 186 |
| Popularity: | 1.82 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2025-03-11 07:23 (UTC) |
I use zfs-dkms from EndeavourOS repos
# /etc/pacman.conf
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
@kstolp - for pkgsums I use a BASH alias: alias pkgsums='updpkgsums && makepkg --printsrcinfo > .SRCINFO' & got into the habit of makepkg -sf before I push changes (after I previously pushed a mismatch)
Patch file didn't pass validity check.
aur@archiso $ aur sync --no-view zfs-dkms zfs-utils
==> Using [aur] repository
-> zfs-dkms (none) -> 2.2.4-1
-> zfs-utils (none) -> 2.2.4-1
==> Retrieving package files
fetch: zfs-utils: already up to date
fetch: zfs-dkms: already up to date
==> Making package: zfs-dkms 2.2.4-1 (Sat 18 May 2024 07:18:03 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found zfs-2.2.4.tar.gz
-> Found zfs-2.2.4.tar.gz.asc
-> Found 2b481b5477d3a95d0eab723c6639f7114e146ae1.patch
-> Found 0001-only-build-the-module-in-dkms.conf.patch
==> Validating source files with sha256sums...
zfs-2.2.4.tar.gz ... Passed
zfs-2.2.4.tar.gz.asc ... Skipped
2b481b5477d3a95d0eab723c6639f7114e146ae1.patch ... FAILED
0001-only-build-the-module-in-dkms.conf.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
Just tried to install 2.2.4-1 version and got this:
==> Validating source files with sha256sums...
zfs-2.2.4.tar.gz ... Passed
zfs-2.2.4.tar.gz.asc ... Skipped
2b481b5477d3a95d0eab723c6639f7114e146ae1.patch ... FAILED
0001-only-build-the-module-in-dkms.conf.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
Could someone please fix the hash of that patch?
kernel 6.8 builds ok with zfs-dkms-2.2.4:
( 4/11) Install DKMS modules
==> dkms install --no-depmod lkrg/0.9.8 -k 6.8.9-hardened1-2-hardened
==> dkms install --no-depmod zfs/2.2.4 -k 6.8.9-hardened1-2-hardened
==> dkms install --no-depmod nvidia/550.78 -k 6.8.9-hardened1-2-hardened
==> depmod 6.8.9-hardened1-2-hardened
on arch-sign-modules I needed to recompile the kernel as gcc-libs just changed to v14
@notjas: your are mixing two things. Patch #15931 is needed for kernel 6.8. Patch #15896 is to notify about the max supported kernel version. They are both not related to each other and patch #15896 is not a fix for anything but just a convenience.
I assume you want to patch zfs to support kernel 6.8. If that is true I suggest you use package zfs-dkms-staging-git instead. This package pulls the branch zfs-2.2.4-staging which supports kernel 6.8 right away. I have it running with kernel 6.8 and it works fine.
I can't seem to figure it out, when I try to makepkg this with the proper https://github.com/openzfs/zfs/pull/15931.patch the packages are only a few mb, 50mb less than what I currently have running. Why on earth was https://github.com/openzfs/zfs/pull/15986 selected instead of the proper fix 😬
@darkbasic, @reaperx7 mixed zfs-dkms and ArchZFS in one comment and it was a bit confusing. '2.2.3-1' in the comment was probably zfs-dkms, '2.2.3-2' was probably ArchZFS which did have more patches: https://github.com/archzfs/archzfs/commit/18e617c824ad4b3c40eb89b087b0d46f1fdf0647. (Unless I failed to decipher the comment too...)
@reaperx7 the PKGBUILD with the patch is https://aur.archlinux.org/packages/zfs-dkms-staging-git not this one
@reaperx7 it doesn't: the maintainer opted for https://github.com/openzfs/zfs/pull/15986 instead.
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)