Arch Linux User Repository

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

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)

Does every kernel update change so much that ZFS needs to be updated as well every time?

Hi ZFSers,

Looks like we are stuck in limbo again with the 6.6-x kernels until upstream releases zfs-2.2.1 with 6.6-x support. Until then, you'll see:

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

Of course, linux-zen throws the same error.

Cheers

@ryanmjacobs:

Note: Packages in the AUR assume that base-devel is installed in the build environment.

https://wiki.archlinux.org/title/Arch_User_Repository#Prerequisites

And there are many kernel and kernel header packages, how would it properly depend on them?

Just FYI: It appears that autoconf is a dependency. I started on a base archiso setup. The dkms dependency pulled in gcc among others. But autoconf should be added. Or maybe just require base-devel.

UPDATE: I just ran into linux-headers missing during the pacman -U stage. But I am not really sure if that one is a zfs-dkms problem... seems like dkms needs to clarify its dependencies better.

Anyone building ZFS for aarch64 can no longer do so without modifying the src to be "GPL licensed", which allows linking non-GPL zfs against the kernel. This is permitted under the GPL if you are building from source and not distributing the resulting binaries. To do so, you can change the license in "META" after building to GPL.

That means that in prepare() you can add after cd-ing:

sed -i 's/CDDL/GPL/g' META

This is referenced here:

https://github.com/openzfs/zfs/issues/11357#issuecomment-1115486147

The DKMS build generates dummy .Po and .Plo files all over the place in /lib/modules/<kernel-version> which are left behind when upgrading to a newer kernel. This can be avoided by also restricting the DKMS make clean to the module directory (i.e. adding CLEAN=make -C module clean to 0001-only-build-the-module-in-dkms.conf.patch). Below is a freshly generated patch for the patch file which also remove a superfluous / (a single space needs to be added to lines 7 and 13):

diff --git a/0001-only-build-the-module-in-dkms.conf.patch b/0001-only-build-the-module-in-dkms.conf.patch
index f2c5d5f..afc2dcc 100644
--- a/0001-only-build-the-module-in-dkms.conf.patch
+++ b/0001-only-build-the-module-in-dkms.conf.patch
@@ -4,14 +4,14 @@ Date: Sun, 28 Oct 2018 15:01:58 -0400
 Subject: [PATCH] only build the module in dkms.conf

 ---
- scripts/dkms.mkconf | 19 ++-----------------
- 1 file changed, 2 insertions(+), 17 deletions(-)
+ scripts/dkms.mkconf | 12 +++---------
+ 1 file changed, 3 insertions(+), 9 deletions(-)

 diff --git a/scripts/dkms.mkconf b/scripts/dkms.mkconf
-index 88c289383..5a859a0e0 100755
+index 0bd383420..965eb5612 100755
 --- a/scripts/dkms.mkconf
 +++ b/scripts/dkms.mkconf
-@@ -28,14 +28,7 @@ PACKAGE_CONFIG="${pkgcfg}"
+@@ -28,14 +28,7 @@ NO_WEAK_MODULES="yes"
  PRE_BUILD="configure
    --prefix=/usr
    --with-config=kernel
@@ -27,12 +27,13 @@ index 88c289383..5a859a0e0 100755
    --with-linux-obj="\${kernel_source_dir}"
    \$(
      [[ -n \"\${ICP_ROOT}\" ]] && \\
-@@ -68,7 +53,7 @@ POST_BUILD="scripts/dkms.postbuild
+@@ -68,7 +61,8 @@ POST_BUILD="scripts/dkms.postbuild
    -t \${dkms_tree}
  "
  AUTOINSTALL="yes"
 -MAKE[0]="make"
-+MAKE[0]="make -C module/"
++CLEAN="make -C module clean"
++MAKE[0]="make -C module"
  STRIP[0]="\$(
    [[ -r \${PACKAGE_CONFIG} ]] \\
    && source \${PACKAGE_CONFIG} \\

Nothing depends on SPL-MODULE or ZFS-MODULE, they are all depending on zfs-dkms or zfs, guess it can be removed

@xiota Those are not package names. Please see the commit message for d364766.