Package Details: zfs-dkms 2.1.13-1

Git Clone URL: (read-only, click to copy)
Package Base: zfs-dkms
Description: Kernel modules for the Zettabyte File System.
Upstream URL:
Licenses: CDDL
Conflicts: spl-dkms
Provides: spl-dkms, SPL-MODULE, zfs, ZFS-MODULE
Replaces: spl-dkms
Submitter: isiachi
Maintainer: kstolp
Last Packager: kstolp
Votes: 156
Popularity: 3.25
First Submitted: 2015-08-31 12:01 (UTC)
Last Updated: 2023-09-28 03:32 (UTC)

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.

==> ERROR: One or more PGP signatures could not be verified!

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 validpgpkeys array. (recommended)

2) Alternatively, you can skip this verification by passing the --skippgpcheck argument to makepkg when building. (not recommended)

Latest Comments

1 2 3 4 5 6 .. 51 Next › Last »

xiota commented on 2023-09-29 02:02 (UTC)

AUR submission guidelines state, "to be renamed", which indicates a future event. Since the rename was approx four years ago, the replaces is no longer relevant.

fryfrog commented on 2023-09-29 01:36 (UTC)

@xiota: Looking at the AUR submission guidelines, the use of replaces=('spl-dkms') seems valid since spl used to be zfs naming and would have been a long past package name, which complies w/ the usage outlined. Why do you think it should be removed? It could be argued that this change took place long enough ago that it shouldn't matter anymore.

xiota commented on 2023-09-29 01:32 (UTC)

Please remove replaces directive to comply with AUR submission guidelines.

itoffshore commented on 2023-09-29 00:38 (UTC)

zfs-dkms 2.1.13-1 builds ok on linux-hardened 6.5.3 (& so does lkrg) - many thanks ;o)

kstolp commented on 2023-09-29 00:34 (UTC)

When requesting changes, please include detailed reasoning for the change.

meithan commented on 2023-09-28 02:35 (UTC)

ZFS 2.1.13, with official support for the linux kernel 6.5, has been released.

xiota commented on 2023-09-20 08:26 (UTC)

Please remove replaces directive. Thank you.

turmoni commented on 2023-09-19 14:40 (UTC)

I don't think there's really much that depends too closely on the kernel version, I just add --ignore=linux --ignore=linux-zen --ignore=linux-headers --ignore=linux-zen-headers to my yay command and I can't think of a single time this has caused an issue for me yet. Obviously this does mean you aren't getting any kernel updates, mind, so if you are in a situation where most security updates are key I guess the LTS kernel is a safer bet.

air-g4p commented on 2023-09-19 07:06 (UTC)

Until zfs gets bumped upstream, I think a better solution is to run linux-lts so you can still keep the rest of your system packages updated.

Otherwise, you'll see something like this:

==> dkms install --no-depmod zfs/2.1.12 -k 6.5.3-hardened1-1-hardened
configure: error: 
        *** None of the expected "bops->release()" interfaces were detected.
        *** This may be because your kernel version is newer than what is
        *** supported, or you are using a patched custom kernel with
        *** incompatible modifications.
        *** ZFS Version: zfs-2.1.12-1
        *** Compatible Kernels: 3.10 - 6.3

Error! Bad return status for module build on kernel: 6.5.3-hardened1-1-hardened (x86_64)
Consult /var/lib/dkms/zfs/2.1.12/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.12 -k 6.5.3-hardened1-1-hardened' exited 10

turmoni commented on 2023-09-16 15:00 (UTC)

Assuming you haven't cleared your pacman cache in the interim and have updated to a non-working kernel version, you should be able to just install the old packages from /var/cache/pacman/pkg rather than having to switch to a different kernel. I always keep an eye on the output of the DKMS build step after major kernel releases and roll back if it fails to build.