@mabod thank you! Exactly what I needed 😃
Search Criteria
Package Details: zfs-dkms 2.3.1-2
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: | 186 |
Popularity: | 1.93 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-03-11 07:23 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- 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 (3)
notjas commented on 2025-03-13 10:04 (UTC)
mabod commented on 2025-03-13 09:23 (UTC) (edited on 2025-03-13 09:39 (UTC) by mabod)
@notjas: Why dont you just edit the META file to contain "Linux-Maximum: 6.99"
The patch is this one: https://github.com/openzfs/zfs/pull/15986/
Also, there is a new config option to disable that behaviour:
--enable-linux-experimental
Allow building against some unsupported kernel
notjas commented on 2025-03-13 09:03 (UTC)
Hi 👋 I'm trying to find how to override the kernel version check, all I remember when it was merged a few months back is a ridiculously long name, intended to make the user read/pay attention. a) I'm having no luck finding that command/switch via google, and I need it for my system b) can I just undo that fucking patch completely which implemented this shit, never have I ever broken my install this way, but that damn patch continues to fuck me repeatedly. Why are we okay being treated as if this were macOS or Windows and we need our hands held...I issue a command I expect it to be executed, any subsequent potential issues are my responsibility... I just want the check gone, permanently if at all possible. The fact that it fails, and then doesn't even fucking tell you how to override... 🫤
fryfrog commented on 2025-02-20 05:52 (UTC)
@mabod: Modifying the META
file or the dkms.conf
file both involve editing the packages file, which doesn't feel great. In addition, if there was an update to the package the modification would not survive and a new kernel would install and the zfs module would not be built.
@yurikoles: It can still be an intended behavior and require research, but the package itself could make it smarter and safer while still maintaining the need for understanding.
I wish I had a good idea of how to do that, I'd suggest it. The package obviously shouldn't just use the option / modify the META
file itself. But it would be nice if there was a route that didn't leave you vulnerable to a zfs-dkms
package update making it not build.
For anyone doing research, no changes beyond updating the META
are required for 6.13.
yurikoles commented on 2025-02-19 20:16 (UTC) (edited on 2025-02-19 20:21 (UTC) by yurikoles)
@fryfrog it's an intended behaviour, people need to do some research before waste their data on ZFS pools and complain about this fact on the upstream GitHub.
mabod commented on 2025-02-19 07:25 (UTC)
@fryfrog: Why would you want to do that? To compile the zfs module for kernel 6.13 you could just edit the META file and set "Linux-Maximum: 6.13".
fryfrog commented on 2025-02-19 05:07 (UTC)
Is there a smart way to add --enable-linux-experimental
to /usr/src/zfs-$pkgver/dkms.conf
? Or maybe is there a smart way this package could make it... maybe not easier, but more discoverable?
fryfrog commented on 2024-12-12 16:52 (UTC) (edited on 2024-12-12 17:05 (UTC) by fryfrog)
Looks like scripts/enum-extract.pl
was removed in 3c5a118, so cp scripts/enum-extract.pl scripts/dkms.postbuild "${dkmsdir}"/scripts/
should be removed from fixed in the PKGBUILD
.
linuxadmin commented on 2024-12-12 08:05 (UTC)
bump, please update to 2.2.7
yurikoles commented on 2024-10-24 08:57 (UTC) (edited on 2024-10-24 09:46 (UTC) by yurikoles)
@ipaqmaster
You seem to be trying to develop an AUR helper while refusing to use AUR API, which .SRCINFO
provides.
depends=()
in this package is indeed in the right place. It's a trick to have a different set of runtime-only dependencies, i.e. those that aren't needed during the package build. So one may build zfs-dkms
without installing zfs-utils
with the very same version first. Most AUR helpers build all new or updated packages being requested before installing them in one go, so this trick works.
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)