@jongeduard, I am aware that it is likely harmless, at least for now. I just wanted to raise the issue with the maintainer.
@eschwartz @jonathon
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: | 188 |
Popularity: | 2.27 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-05-03 09:40 (UTC) |
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 66 Next › Last »
@jongeduard, I am aware that it is likely harmless, at least for now. I just wanted to raise the issue with the maintainer.
@eschwartz @jonathon
@debohman I noticed the same. Some searching on the internet will show you more recent examples elsewhere around DKMS.
In the DKMS project itself on GitHub I found this: https://github.com/dell/dkms/pull/164.
So it's just a change there. When you click on "#158" on that page, you'll find that it's apparently a change in order to remove "distro specific packaging" related things.
Anyway, it's just a warning, not a real problem and everythings works fine.
When I just upgraded my system, I received the following warning from dkms:
Deprecated feature: REMAKE_INITRD
The system was upgraded to dkms-3.0.2-1.
thank you for the update! Great! :-)
On the topic of swapping between zfs-utils from archzfs vs eschwartz (the one in AUR), a word of warning!
The initcpio hooks in in https://aur.archlinux.org/cgit/aur.git/tree/?h=zfs-utils is not the same as in https://github.com/archzfs/zfs-utils If you rely on encrypted root volume, the initcpio in zfs-utils AUR package will not work, since it is lacking the zfs loadkey call. This is present in archzfs version though. Read more here: https://github.com/eli-schwartz/pkgbuilds/issues/30
@fryfrog, that is very useful. It wasn't commented in my paru.conf
, but I added it.
@dhathaway, since you use paru
, you can edit /etc/paru.conf
and uncomment the line with BatchInstall
, that way it'll package up the AUR packages, but install them all together at the end! This is possible in yay
too, but I don't know how.
@fryfrog you are right that this is mentioned many times in the past here. You just have to know what to look for, which I did not. Thanks for the hint.
Since it has been many pages since a fix was posted, here is what I did:
I started in ~/.cache/paru/clone/
since I prefer paru to yay.
cd zfs-dkms
makepkg -s
cd ../zfs-utils/
makepkg -s
sudo pacman -U ~/.cache/paru/clone/zfs-dkms/zfs-dkms-2.1.1-1-any.pkg.tar.zst \
~/.cache/paru/clone/zfs-utils/zfs-utils-2.1.1-1-x86_64.pkg.tar.zst
sudo vim /etc/pacman.conf
paru
sudo reboot
Note that I had gone back to a previous kernel, so I also took linux
and linux-headers
out of the IgnorePkg
so that I could upgrade the kernel finally. That is why I edited pacman.conf
.
@dhathaway, you have to install/update both packages at the same time. This has always been true. Read further back if you need help understanding, it is a common problem.
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, as declared in the META file.
Options if your Linux kernel's version is not within that range:
1) Switch to another Linux kernel, such as
linux-lts
.2) Prevent your kernel package from upgrading to an unsupported version until OpenZFS increases the maximum supported kernel version.
3) Modify this package to support your kernel by patching it on your local machine.
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)