| 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) |
autoconf 2.71 packaged in testing.
Tried building 2.0.2 and made the package but couldn't get DKMS to compile. Could be on my end. Package might need tweaking.
Seems to not generate the Makefile. I'm bad at finding the relevant logs (past make.log from DKMS).
I pinged the autoconf maintainer on the 25th. He was busy, but 2.71 got released today. Waiting for it to get packaged, then I'll test updating this package.
+1 on the upstream autoconf issue.
I also noticed that dkms-install recompiles the whole shebang in the post-transaction hooks (i.e Install DKMS modules stage) even though all of the modules were already built. On "slower" systems (1.8GHz Atom CPUs for example) with multiple kernels, this adds several extra hours for the installation as it essentially doubles the work for no reason.
There is no commandline output during this time.
Further, said hooks expect dpkg-architecture to be installed, which is usually not the case on non-debian systems.
@iusrlinearb thank you for reassuring me mate. I have updates my systems today and besides that "warning" it works like a charm :)
Thanks for keeping on top of it, my 2 systems appreciate it!
The update doesn't fix the autoconf 2.70 error. It does fix a separate issue, which are some additional autoconf 2.70 warnings.
There was supposed to be a new autoconf 2.70.1 / 2.71 release "later this week", but that was last week, so maybe the autoconf maintainer didn't have time either. ;)
@storm.continuity, you don't need to worry about it. It's typical to take a bit of time from an upstream to getting an update for any package because testing, home schedules etc.
I wouldn't bother switching away from this package unless there is something in 2.0.1 which is critical to you, looking at the release notes I don't see much of interest other than the autoconf fix which will be welcome for those of us who have downgraded that package.
Please delete this if this is not the right place to ask but: the package has been flagged out of date. Do i have to worry about it or is it "normal"? Should i switch to the git version? Thanks
autoconf 2.70 is now in core.
For anyone else who needs to downgrade, pacman -U https://archive.archlinux.org/packages/a/autoconf/autoconf-2.69-7-any.pkg.tar.zst should do it.
+1 confirm that downgrade to autoconf 2.69 is needed presently for makepkg until zfs autoreconf fix is patched
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)