Package generated with mkbmdeb fails to be installed when using kernel mainline build
Bug #1835429 reported by
Dimitris Aragiorgis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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-
It seems that the `/etc/dkms/
Would it make sense to extend Depends with a linux-image-
[1] https:/
To post a comment you must log in.
I think editing the systemwide template should be discouraged. Is it perhaps an issue of unsigned- XXX package? Shouldn't it simply Provide linux-image-XXX?
the linux-image-
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: version- abiname[ -featureset] -flavour- unsigned
```
linux-image-
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. unsigned- 5.2.0-050200rc6 -generic_ 5.2.0-050200rc6 .201906222033_ amd64.deb?
```
Does the above hold for linux-image-
I tend to believe that his is more an issue with the kernel mainline build rather than with DKMS.