Package: dkms Version: 2.2.0.3-5 It's great to see that Bug#554843 is finally closed and 'dkms mkbmdeb' builds a standalone binary package. Thanks!
Unfortunately, this doesn't help anything that depends on the -dkms package itself, or a -modules virtual package For example, the 'zfs-zed', 'zfs-initramfs', 'zfs-dracut', and 'zfsutils-linux' packages all have: Depends: [...], zfs-modules | zfs-dkms, zfsutils-linux The 'zfs-dkms' package has: Provides: zfs-modules The 'zfs-dkms-bin' package built by 'dkms mkbmdeb -m zfs -v 0.6.5.7' has only: Package: zfs-dkms-bin Version: 0.6.5.7 Architecture: amd64 Maintainer: Dynamic Kernel Modules Support Team <pkg-dkms-ma...@lists.alioth.debian.org> Installed-Size: 3086 Depends: linux-image-4.6.0-1-amd64 Section: misc Priority: optional This does not satisfy the dependencies of 'zfs-zed' or the others. The binary module package should probably have a Provides: line containing either or both of the 'Package:' and 'Provides:' fields of the -dkms package it replaces. BTW, The same is true for the 'virtualbox' package, which depends on 'virtualbox-dkms' or 'virtualbox-modules'. A quick check with apt-cache search -n -- -dkms | cut -d' ' -f1 | xargs -n1 apt-cache rdepends | grep -v '^[R ]' seems to indicate that this will be a problem with ALL -dkms packages. craig PS: one current work-around is to use the 'equivs' package to build a dummy package which has, for example: Depends: zfs-dkms-bin Provides: zfs-modules, zfs-dkms -- craig sanders <c...@taz.net.au>