Package Details: zfs-dkms 0.7.13-1

Git Clone URL: https://aur.archlinux.org/zfs-dkms.git (read-only)
Package Base: zfs-dkms
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://zfsonlinux.org/
Licenses: CDDL
Provides: zfs
Submitter: isiachi
Maintainer: eschwartz
Last Packager: eschwartz
Votes: 70
Popularity: 0.868389
First Submitted: 2015-08-31 12:01
Last Updated: 2019-03-05 02:22

Dependencies (4)

Required by (12)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

eschwartz commented on 2019-03-29 06:50

@milaxnuts,

This will never, ever be implemented. See https://wiki.archlinux.org/index.php/User:Apg#makepkg:_shallow_git_clones for more details on why makepkg cannot do this, and the long list of rejections.

The only option that is acceptable is if you convince upstream to sign their tarballs. Currently, checking PGP signatures for the zfsonlinux project requires using git, but there's no other reason to prefer it. This would drop the download size to 6.5MB (8MB for the 0.8 release candidate).

EDIT: they may in fact do this: https://github.com/zfsonlinux/zfs/issues/8557

milaxnuts commented on 2019-03-29 06:08

please use "git shallow clone" to save traffic.

81.64 MiB :full clone
  5.56 MiB :shallow clone

--> less by factor 15

sample call:

git clone --depth=1 --recurse-submodules -b zfs-0.7.13 https://github.com/zfsonlinux/zfs

eschwartz commented on 2019-03-28 18:28

@greencopper,

This package requires reading the documentation on how to run the makepkg command. There are no exceptions.

greencopper commented on 2019-03-28 00:23

UPDATE: Sorry, I complete forgot about the key part when using AUR.

==> Verifying source file signatures with gpg...
    zfs git repo ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!

karcher commented on 2019-03-11 19:10

@eschwartz: I've uninstalled all 3 packages: spl-dkms, zfs-dkms and zfs-utils and then reinstalled zfs-dkms. It looks fine now.

eschwartz commented on 2019-03-11 05:42

That would do it, I guess.

The manpage for dkms install observes regarding dependencies that "Note that this directive is only advisory; missing or broken dependencies cause non-fatal warnings."

The pacman hook implements its own sort ordering by checking dkms status for dependencies, and will fail if dependencies are missing, which is unlike the default dkms behavior.

vanja_z commented on 2019-03-11 04:40

Thank you kindly for the advice Eli, it resolved my issue! I had an old version of spl-dkms kicking around for some reason, after I manually removed it with

dkms remove spl/0.7.9 --all

then the pacman install worked perfectly as usual! I have no idea how that went wrong, it looks like dkms gets confused when there are multiple versions as you suspected. Thanks again!

ps. I also have no idea why that specific version of spl was left behind? Perhaps a failed upgrade earlier. I will leave this comment in case somebody else encounters an issue that they should check what dkms modules are available.

eschwartz commented on 2019-03-11 02:25

@karcher,

AUR helpers are notoriously unreliable when it comes to handling versioned dependencies. You will not be able to partially update the zfs packages; you need to build them without installing them, then install the whole set together... (EDIT: Or alternatively, uninstall zfs-dkms in order to allow its dependencies to be updated, then reinstall the new version of zfs-dkms.)

@vanja_z,

It is impossible for the zfs module to build if the spl module is not built, but if the spl module is built, then the pacman hook will work. I do know that it works for me... without being able to troubleshoot the internal state of dkms, I cannot say more.

However, it definitely has nothing to do with dkms-sorted.

So as far as I can tell, what you're saying is happening is... not impossible, but nearly so. I don't know why the pacman hook would not work, but dkms might work if it is incorrectly and dangerously building against an old built version of spl, as the zfs-dkms build system might be fooled into thinking that the old version is sufficient.

In general, reinstalling both spl-dkms and zfs-dkms will cause the hooks to trigger again, thereby doing a dkms install for first spl, then zfs -- which should work, as you're setting it up to rebuild from scratch.

Not sure what else to say.

karcher commented on 2019-03-11 01:42

Hi all,

I'm getting an error during the latest update:

...
:: 3 Packages to upgrade.
3  aur/spl-dkms   0.7.12-1 -> 0.7.13-1
2  aur/zfs-dkms   0.7.12-2 -> 0.7.13-1
1  aur/zfs-utils  0.7.12-1 -> 0.7.13-1
...
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing spl-dkms (0.7.13-1) breaks dependency 'spl-dkms=0.7.12' required by zfs-dkms

Any ideas what's wrong?

vanja_z commented on 2019-03-08 13:28

I do understand that this is how the process is meant to work however it is not working on my system. My system is up to date and I have the matching version of spl-dkms (0.7.13). ZFS works fine after I manually dkms install the module. Does anybody have any ideas what could be going wrong or how to trouble shoot? Does this have something to do with the dkms-sorted package that used to exist?