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)

Recent kernel change did away with get_ds() in favor of KERNEL_DS.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.1.3&id=736706bee329

If you need to, edit line 611 of /usr/src/spl-0.7.13/module/spl/spl-vnode.c and change:

set_fs(get_ds());

to

set_fs(KERNEL_DS);

then run

dkms install spl/0.7.13 -k $(uname -r)

dkms install zfs/0.7.13 -k $(uname -r)

0.7.13 only compatible with kernels up to 5.0, not 5.1. See here ... https://github.com/zfsonlinux/zfs You should wait for 0.8 release of ZoL before using kernel 5.1

@eblau I have this too. These spl- and zfs- dkms packages often break when a new kernel comes out. Just downgrade your kernel (linux, linux-headers) until spl-dkms is updated.

You may want to consider adding linux and linux-headers to IgnorePkg= in /etc/pacman.conf. Just update them manually, once you see that spl and zfs are working.

I'm hitting build errors after upgrading to linux-5.1.2.arch1-1:

/var/lib/dkms/spl/0.7.13/build/module/spl/spl-vnode.c: In function ‘vn_set_pwd’:
/var/lib/dkms/spl/0.7.13/build/module/spl/spl-vnode.c:611:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
  set_fs(get_ds());
         ^~~~~~
         get_fs
/var/lib/dkms/spl/0.7.13/build/module/spl/spl-vnode.c:611:9: error: incompatible type for argument 1 of ‘set_fs’
  set_fs(get_ds());
         ^~~~~~~~
In file included from ./include/linux/uaccess.h:11,
                 from ./include/linux/poll.h:12,
                 from ./include/linux/ring_buffer.h:7,
                 from ./include/linux/trace_events.h:6,
                 from ./include/trace/syscall.h:7,
                 from ./include/linux/syscalls.h:86,
                 from /var/lib/dkms/spl/0.7.13/build/include/sys/vnode.h:29,
                 from /var/lib/dkms/spl/0.7.13/build/module/spl/spl-vnode.c:28:
./arch/x86/include/asm/uaccess.h:29:40: note: expected ‘mm_segment_t’ {aka ‘struct <anonymous>’} but argument is of type ‘int’
 static inline void set_fs(mm_segment_t fs)
                           ~~~~~~~~~~~~~^~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:276: /var/lib/dkms/spl/0.7.13/build/module/spl/spl-vnode.o] Error 1

I assume this is an issue on the ZFS on Linux side but a quick search on the Github repo doesn't show anything. Anyone else hitting this?

@milaxnuts,

This will never, ever be implemented. See https://wiki.archlinux.org/index.php/User:Apg#makepkg:_shallow_git_clones for more details on why makepkg cannot do this, and the long list of rejections.

The only option that is acceptable is if you convince upstream to sign their tarballs. Currently, checking PGP signatures for the zfsonlinux project requires using git, but there's no other reason to prefer it. This would drop the download size to 6.5MB (8MB for the 0.8 release candidate).

EDIT: they may in fact do this: https://github.com/zfsonlinux/zfs/issues/8557

please use "git shallow clone" to save traffic.

81.64 MiB :full clone
  5.56 MiB :shallow clone

--> less by factor 15

sample call:

git clone --depth=1 --recurse-submodules -b zfs-0.7.13 https://github.com/zfsonlinux/zfs

@greencopper,

This package requires reading the documentation on how to run the makepkg command. There are no exceptions.

UPDATE: Sorry, I complete forgot about the key part when using AUR.

==> Verifying source file signatures with gpg...
    zfs git repo ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!

@eschwartz: I've uninstalled all 3 packages: spl-dkms, zfs-dkms and zfs-utils and then reinstalled zfs-dkms. It looks fine now.

That would do it, I guess.

The manpage for dkms install observes regarding dependencies that "Note that this directive is only advisory; missing or broken dependencies cause non-fatal warnings."

The pacman hook implements its own sort ordering by checking dkms status for dependencies, and will fail if dependencies are missing, which is unlike the default dkms behavior.