Package Details: zfs-dkms 2.3.0-2

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: 185
Popularity: 2.64
First Submitted: 2015-08-31 12:01 (UTC)
Last Updated: 2025-01-14 06:47 (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 .. 63 Next › Last »

fryfrog commented on 2025-02-20 05:52 (UTC)

@mabod: Modifying the META file or the dkms.conf file both involve editing the packages file, which doesn't feel great. In addition, if there was an update to the package the modification would not survive and a new kernel would install and the zfs module would not be built.

@yurikoles: It can still be an intended behavior and require research, but the package itself could make it smarter and safer while still maintaining the need for understanding.

I wish I had a good idea of how to do that, I'd suggest it. The package obviously shouldn't just use the option / modify the META file itself. But it would be nice if there was a route that didn't leave you vulnerable to a zfs-dkms package update making it not build.

For anyone doing research, no changes beyond updating the META are required for 6.13.

yurikoles commented on 2025-02-19 20:16 (UTC) (edited on 2025-02-19 20:21 (UTC) by yurikoles)

@fryfrog it's an intended behaviour, people need to do some research before waste their data on ZFS pools and complain about this fact on the upstream GitHub.

mabod commented on 2025-02-19 07:25 (UTC)

@fryfrog: Why would you want to do that? To compile the zfs module for kernel 6.13 you could just edit the META file and set "Linux-Maximum: 6.13".

fryfrog commented on 2025-02-19 05:07 (UTC)

Is there a smart way to add --enable-linux-experimental to /usr/src/zfs-$pkgver/dkms.conf? Or maybe is there a smart way this package could make it... maybe not easier, but more discoverable?

fryfrog commented on 2024-12-12 16:52 (UTC) (edited on 2024-12-12 17:05 (UTC) by fryfrog)

Looks like scripts/enum-extract.pl was removed in 3c5a118, so cp scripts/enum-extract.pl scripts/dkms.postbuild "${dkmsdir}"/scripts/ should be removed from fixed in the PKGBUILD.

linuxadmin commented on 2024-12-12 08:05 (UTC)

bump, please update to 2.2.7

yurikoles commented on 2024-10-24 08:57 (UTC) (edited on 2024-10-24 09:46 (UTC) by yurikoles)

@ipaqmaster

You seem to be trying to develop an AUR helper while refusing to use AUR API, which .SRCINFO provides.

depends=() in this package is indeed in the right place. It's a trick to have a different set of runtime-only dependencies, i.e. those that aren't needed during the package build. So one may build zfs-dkms without installing zfs-utils with the very same version first. Most AUR helpers build all new or updated packages being requested before installing them in one go, so this trick works.

ipaqmaster commented on 2024-10-24 00:55 (UTC) (edited on 2024-10-25 00:05 (UTC) by ipaqmaster)

I can't source the .SRCINFO file for my variables. Are you suggesting I write a parser from scratch for that instead of moving the depends=() variable outside of the package() function?

This is the only package I put together in over 700 which has the depends=() array hidden in the package() function like this.

Ok. I'm not going to make this pipeline bother AUR's API any more than needed. I'll write a .SRCINFO parser. Wish me luck.

thaewrapt commented on 2024-10-23 08:33 (UTC)

https://wiki.archlinux.org/title/.SRCINFO is what you need instead of evaluating the PKGBUILD yourself. It's indeed the results of the said evaluation.

ipaqmaster commented on 2024-10-22 23:43 (UTC) (edited on 2024-10-22 23:47 (UTC) by ipaqmaster)

Can depends=("zfs-utils=${pkgver}" 'dkms') be moved from the package() function to the main variables area at the top? I'm trying to put together an aur package which depends on zfs (Sticking with zfs-dkms) but sourcing the PKGBUILD file doesn't define a $depends variable and the package installation fails because zfs-utils doesn't get sought after.

If there's a correct way to evaluate this PKGBUILD to know that zfs-utils must also be built for zfs-dkms to install correctly please let me know.

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