You are not logged in.
I believe that there is a requirement that the version of these two packages must match for ZFS to function properly.
They often change versions together although one occasionally lags behind, being updated days or weeks later.
Currently, they both changed versions from 2.2.7 to 2.3.0 at the same time on 2025-01-14.
This new release has a fantastic new feature which I wish to utilize immediately.
However, the minor version (distro patch?) of these two packages are different:
aur/zfs-dkms 2.2.7-1 -> 2.3.0-2
aur/zfs-utils 2.2.7-1 -> 2.3.0-1
I've always assumed that the appended -n was also required to match.
However, I don't know that to be true.
Can anyone share insight into the importance of the appended -n in the above package versions?
Thank you,
H.
Last edited by heidegger (2025-01-25 18:07:57)
Offline
the -n is the pkgrel, so a rebuild of the package with (normally) the same underlying source code, either due to a change in the PKGBUILD or a rebuild (e.g. non-dkms kernel modules will have high pkgrel numbers since they need rebuilding with every new kernel) https://wiki.archlinux.org/title/PKGBUILD#pkgrel
So yes, this should normally not have an effect on the actual software's compatibility, and is an indicator of a distro (Arch) specific version bump.
Offline
Thank you for your answer and the clarification in terminology... pkgrel!
Offline
Excellent! The changelog had the answer all along.
It almost seems obvious now.
Offline
although the aur version pretty much just links back to github you may have a look at its upstream source https://github.com/archzfs/archzfs as this minor patch seems some out of tree own modification not commibg from archzfs base
Offline