Package generated with mkbmdeb fails to be installed when using kernel mainline build

[Dimitris Aragiorgis]

Using latest kernel mainline build, e.g. [1], the binary package generated with `dkms mkbmdeb`
fails to be installed since it depends on linux-image-XXX but only linux-image-unsigned-XXX is available (which by the way conflicts with linux-image-XXX).

It seems that the `/etc/dkms/template-dkms-mkbmdeb/debian/control` adds this explicit dependency.

Would it make sense to extend Depends with a linux-image-KERNEL_VERSION | linux-image-unsigned-KERNEL_VERSION or should the end user patch the systemwide template before running dkms?

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/

[Dimitris Aragiorgis (dimitris.aragiorgis)]

I think editing the systemwide template should be discouraged. Is it perhaps an issue of
the linux-image-unsigned-XXX package? Shouldn't it simply Provide linux-image-XXX?

I am also not sure why some arch specific builds (e.g., amd64, arm64) have an -unsigned binary
package and other don't (e.g., i386).

Copying from https://kernel-team.pages.debian.net/kernel-handbook/ch-packaging.html#s-arch-dep:
```
linux-image-version-abiname[-featureset]-flavour-unsigned

This package contains the binary kernel image and pre-built binary modules for a particular arch/featureset/flavour combination, that are meant to be signed and copied into a package without the -unsigned suffix. There is normally no need to install these packages.
```
Does the above hold for linux-image-unsigned-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb?

I tend to believe that his is more an issue with the kernel mainline build rather than with DKMS.