To solve the "Unknown public key" issue, just add the PGP keys of the ZFS on Linux maintainers like described here: https://github.com/zfsonlinux/zfs/wiki/Signing-Keys.
Search Criteria
Package Details: zfs-dkms 2.2.6-1
Package Actions
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: | 179 |
Popularity: | 6.41 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2024-09-05 04:42 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 63 Next › Last »
othiman commented on 2018-11-02 21:30 (UTC)
mrueg commented on 2018-11-02 21:05 (UTC) (edited on 2018-11-02 21:28 (UTC) by mrueg)
If you get the message 'Unknown public key 6AD860EED4598027' when trying to install this, see here: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking . You need to import the mentioned key first. ( A (not very satisfying and usually a bad idea) workaround is to remove the '?signed' at the end of the repo URL. )
eschwartz commented on 2018-10-31 15:38 (UTC)
I don't understand this thing at all, as splat.ko is provided by spl-dkms alongside the spl module itself, but splat is also a binary which interacts with the kernel module of the same name.
And splat is a testsuite, it certainly doesn't need to be in the initcpio. The error message should be harmless-ish, mkinitcpio is just warning you that it couldn't find one of the files and therefore if your boot process actually relies on the file in question, then it will have errors.
But, this should really be removed from the install hook altogether, along with a couple python scripts that I literally don't comprehend their presence.
solnce commented on 2018-10-31 14:05 (UTC)
There is still one issue. I have a machine with root on ZFS. With the current packages, I cannot build the initial ramdisk, because the module splat
, formerly provided by spl-utils
, is missing.
~ [1]$ sudo mkinitcpio -p linux-zen
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 4.17.14-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [encrypt]
-> Running build hook: [zfs]
==> ERROR: file not found: `splat'
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-zen.img
==> WARNING: errors were encountered during the build. The image may not be complete.
eschwartz commented on 2018-10-30 20:20 (UTC)
The provides has been re-added, as also mentioned in the zfs-utils comments.
I'm not going to remove security checks though, especially not for a high-profile package like a kernel module. If following the instructions from https://wiki.archlinux.org/index.php/Makepkg#Signature_checking is a show-stopper for people, then so be it. Hopefully this won't be a big problem for people, though, especially as zfs is a fairly technical thing to use to begin with.
othiman commented on 2018-10-30 15:05 (UTC)
Hi,
in the latest version the "provides=("zfs")" was deleted and so I wasn't able to update the packages since the zfs-snap-manager has a dependency on zfs.
An addition I had to add the pgp keys like described here: https://github.com/zfsonlinux/zfs/wiki/Signing-Keys. This might be a stopper for a lot of people.
Best regards, othiman
eschwartz commented on 2018-10-30 02:28 (UTC)
Sorry for the momentary absence of the package. I split it out because I didn't see the purpose of combining them, but while I successfully uploaded the new dkms package, the replacement utils package failed to upload because of my current terrible internet situation.
It's up now and should work, although as I don't use zfs I can only test that the modules compile successfully. But it's hopefully a lot more generic and better split.
solnce commented on 2018-10-28 22:06 (UTC) (edited on 2018-10-28 22:09 (UTC) by solnce)
@eschwartz: Am I correct to assume that zfs-utils is now replaced by zfs-utils-common, or are you going to upload a new version of zfs-utils? BTW: Thanks for maintaining this!
karcher commented on 2018-10-25 18:45 (UTC)
@allspark : Thanks!
I finally tried to built zfs-dkms and spl-dkms (v0.7.11) with clean-chroot-manager and installed the 4 generated packages successfully. I had to use the -f option to import my zvols but after I rebooted one more time everything seems to be OK.
allspark commented on 2018-10-24 20:10 (UTC)
i changed the version in the PKGBUILD, built and installed it
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.
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 tomakepkg
when building. (not recommended)