Hi, I can't update because pgp isn't wrong, can I fix it?
This is error: error: archzfs: the signature of "ArchZFS Bot buildbot@archzfs.com" is not valid
I have temporarily solved it by putting SigLevel = Never
Git Clone URL: | https://aur.archlinux.org/zfs-linux.git (read-only, click to copy) |
---|---|
Package Base: | zfs-linux |
Description: | Kernel headers for the Zettabyte File System. |
Upstream URL: | https://openzfs.org/ |
Keywords: | kernel linux openzfs zfs |
Licenses: | CDDL |
Conflicts: | spl-dkms, spl-dkms-git, spl-headers, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-headers |
Provides: | spl-headers, zfs-headers |
Submitter: | demizer |
Maintainer: | lightdot |
Last Packager: | lightdot |
Votes: | 276 |
Popularity: | 0.121682 |
First Submitted: | 2016-04-21 08:45 (UTC) |
Last Updated: | 2025-09-07 16:34 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 80 Next › Last »
Hi, I can't update because pgp isn't wrong, can I fix it?
This is error: error: archzfs: the signature of "ArchZFS Bot buildbot@archzfs.com" is not valid
I have temporarily solved it by putting SigLevel = Never
Dracul, it gets updated regularly, but sometimes the minor version upgrades come quickly enough that testing isn't complete before the maintainer releases, so those get skipped. Personally, I have a notification set on this package so I know when a new version is released and try to prioritize updating my systems soon thereafter.
Hi, how often is it updated with respect to the kernel?
Thanks for the info.
@idimitro OpenZFS has some problems at upstream (FreeBSD, Dacrut, Debian, etc). These errors needs to be fixed in order to publish the OpenZFS version 2.1.5, that supports kernel 5.18.x and 5.19.x: https://github.com/openzfs/zfs/pull/13532
Hi, any hope of getting the builds working? The zfs kernel has never been that slow.
I just wanted to let you know, that Buildbot wasn't able to push the latest build to the AUR.
Cannot build even in a chroot.
@Egns if you want to build the zfs-linux
package yourself you can use a chroot jail to perform the actual build. Update the kernel in the chroot to the version required by the build.
https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
From there you can copy the package file to a custom local repository and add the repository to your /etc/pacman.conf
.
https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Custom_local_repository
There seems to be a bug where zfs mount
/mount
of encrypted datasets/zvols fail silently (https://github.com/openzfs/zfs/issues/12418). The upstream bug report doesn't seem to have gotten any attention in two months; does anyone know if it's an issue local to Arch?
Pinned Comments
lightdot commented on 2025-02-04 21:19 (UTC) (edited on 2025-08-27 08:58 (UTC) by lightdot)
This package will be kept in sync with the latest openzfs stable release and the kernels officially supported by it.
For the supported kernel versions, refer to the respective openzfs release notes (LINK).
E.g., openzfs 2.3.4 supports kernel versions 4.18 - 6.16. When kernel 6.17 is released for Arch, zfs-linux will not be updated until the openzfs project announces that it's compatible. This will most likely happen with the next openzfs release.
Kernel compatibility of the upcoming openzfs release can be seen in their META file (LINK).
For those wishing to use openzfs with unsupported kernels, do note that this can lead to serious issues, including data loss, even though such a zfs-linux package might build and install cleanly. Have reliable backups and use such a package at your peril.
Please do not mark this package as out of date without checking the kernel compatibility first. Thank you!