| 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) |
qs9rx,
That's an integral part of setting up dkms(see wiki). There's no provides for the various linux-*-headers packages, so specifying an explicit dependency on linux-headers would prevent people from using this package with kernel variants like linux-lts.
This is missing the dependency for kernel headers. Without linux-headers installed all I got was:
==> Unable to install module zfs/2.0.4 for kernel *: Missing kernel headers.
Works for me with simple pkgver bump to 2.0.4
Note 5.12 is not supported despite mentions in git log
Might work if you don't care about your data and want to bypass the configure check
Updates are quite an issue with this package, because it has the zfs-uitls version hardcoded in its dependencies. (Not sure whether this is necessary or not.)
Well, once upon a time they both built from the same PKGBUILD, thus inconveniencing users who wanted the utils but also a built variant of the module, e.g. zfs-linux...
Given there's no real guarantee from the upstream project that you can use any module version with any utils version, I think it's reasonable to expect them to be somewhat synced... this is not a problem if your AUR helper supports building multiple packages and installing them at the end. Or if you build packages into a custom repo, like aurutils does.
@andrej, you should build both packages first & then install them in one call to pacman -U
Updates are quite an issue with this package, because it has the zfs-uitls version hardcoded in its dependencies. (Not sure whether this is necessary or not.) As a consequence, one has to remove zfs-dkms, then do a system upgrade involving zfs-utils and then reinstall zfs-dkms. If something goes wrong during the update and a reboot occurs, one may end up without ZFS support, which may be a slight inconvenience or an unbootable system, depending on your ZFS setup.
Now that autoconf 2.71 and glibc 2.33 are out of testing this should install normally.
greencopper, see the comments below. I don't think you're on [testing] as you may need to be.
==> Starting prepare()...
patching file scripts/dkms.mkconf
Hunk #1 succeeded at 26 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 60 with fuzz 1 (offset -3 lines).
configure.ac: error: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION or AM_GNU_GETTEXT_REQUIRE_VERSION
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'
configure.ac:48: installing 'config/compile'
configure.ac:42: installing 'config/missing'
==> ERROR: A failure occurred in prepare().
Aborting...
Manually updating the package to version 2.0.2 works if this patch is added. It is a workaround for an autoconf issue that will be fixed in a new version, which is not available yet.
After installation, I had to manually copy config/compile from the sources to /usr/src/zfs-2.0.2/config/. A one-time manual recompilation of the DKMS module allowed me to build the module for my new kernel. I used:
dkms install -m zfs -v 2.0.2 -k 5.4.94-1-lts
Probably these steps can be integrated in PKGBUILD.
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
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)