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)

I had trouble making this package...

ERROR: 0001-only-build-the-module-in-dkms.conf.patch was not found in the build directory and is not a URL.

So I get the patch file from the Sources list on this page, and I still can't build it...

0001-only-build-the-module-in-dkms.conf.patch ... FAILED

ERROR: One or more files did not pass the validity check!

Then I figured if I just cut out some of the junk in the patch file (it looks like a simple copy-paste of an entire email someone got), then it would accept the patch... nope (but I kept my changes). So, then I figured out I need to run makepkg -g >> PKGBUILD to update the hash for the patchfile. Ok... I do that, then I get a new error:

Verifying source file signatures with gpg... zfs-2.1.4.tar.gz ... FAILED (unknown public key 6AD860EED4598027) ERROR: One or more PGP signatures could not be verified!

So, then I figure out I have to add that gpg key to my key ring blindly (which defeats the purpose of using gpg, but whatever -- who is Tony Hutter and why should I trust him? Whose gpg key should I expect? No idea, but I have no choice if I want to continue EDIT: There IS a line about him in PKGBUILD file, so my bad) using the command as the non-root user I'm using the build the package:

gpg --receive-keys 6AD860EED4598027

And now finally I can build the package.

Thoughts:
1) The patch is required to make the package, and it's from the year 2018... so it should probably just be included at this point, right? Can't it be set up to auto-download the file at least? 2) Why I should dis/trust Tony Hutter's GPG key for the zfs-2.1.4.tar.gz file should probably be included in the PKGBUILD file. EDIT: There is a comment line in the PKGBUILD about trusting Tony Hutter, so that's fine. I didn't see it while using a standard tty terminal.

zfs-dkms 2.1.4-1 all ok with 5.15.27.hardened1-1

I had to clean up some old config with rm -rf /var/lib/dkms/zfs/2.1.2 to fix Unable to build an empty module

@jonathon Correct, also with archzfs now. Tried it again. Issues solved with 5.15.23-2-lts.

If you're having an issue at this point it's because you have a partial upgrade. All kernels have been built with GCC 11.2.0, and DKMS will rebuild the ZFS module accordingly.

Currently I am using the archzfs version (but also keeping a copy of this AUR one in a folder so that I can switch things easily), but yesterday the update to LTS kernel 5.15.23-1-lts gave me that exact same ZFS build error, about that it could not build an empty module (I verified it by manually running the dkms build command again to see it's output). Luckily on the regular kernel 5.16.9-arch1-1 it did still build fine (with that same archzfs version) in my case. So with having both kernels installed on my system it wasn't a direct issue. But if it's also gonna happen with the regular kernel.

https://bbs.archlinux.org/viewtopic.php?pid=2022195#p2022195

did some experiments and concur largely with @razielgn re: synchronous changes:

• build failed with gcc-11.2.0-3, gcc-libs-11.2.0-3, binutils-2.38-3, linux-lts-5.15.23
• build failed with gcc-11.2.0-3, gcc-libs-11.2.0-3, binutils-2.38-3, linux-lts-5.15.22
• build failed with gcc-11.1.0-3, gcc-libs-11.1.0-3, binutils-2.36-3, linux-lts-5.15.23
• build succeeded with gcc-11.1.0-3, gcc-libs-11.1.0-3, binutils-2.36-3, linux-lts-5.15.22

My system was running gcc-11.1.0-1 and binutils-2.36.1-3 and linux-5.15.13 and zfs was working fine. As soon as I upgraded to linux-5.16.8 nfs-dkms failed to build. I downgraded the kernel back to 5.15.13 and everything is fine again. So maybe it is just the kernel not the gcc and binutils?

dkms apparently cannot build 2.1.2-2 with gcc 11.2 and binutils 2.38: I get "checking whether modules can be built... no". make was failing due to missing target when invoked (sorry, I lost the logs). It's easy to reproduce if you include [testing] packages. I downgraded gcc to 11.1, binutils to 2.36 and got it working again. Also cannot build zfs module with gcc 11.1/bintuils 2.36 for linux-tls 5.15.23 (also in testing), I guess the maintainers have made synchronous changes across all those packages.