Hello Debian Kernel Team,
Recently I needed to build packages for the latest mainline kernel to post some
logs to kernel.org bugzilla
(https://bugzilla.kernel.org/show_bug.cgi?id=221319). I followed the kernel
handbook (chapter 4 mainly) and it generally went pretty smoothly and I posted
a mini-howTo on Debian Forums: https://forums.debian.net/viewtopic.php?t=166381
The only bit that I'm missing is generating `linux-image-${VERSION}-amd64`, so
to work-around this, after installing the built packages, I manually call
`linux-run-hooks image postinst`. From what I understand, `linux-signed` /
`linux-image-${VERSION}-amd64` is generated by Debusine based on
`linux-image-amd64-signed-template`, so I was wondering if:
a) ...I can fake this process somewhat and generate
`linux-image-${VERSION}-amd64` locally using some scripts and ideally also sign
the kernel for example with my dkms MOK, or...
b) ...if the above is over-complicated or not feasible, is it sufficient (for
the purpose of setting-up / cleaning-up of kernel images) to create a dummy
package that depends on `linux-binary` (and others) with maintainer-scripts
generated from `debian/templates/image.p*` templates? If so, is there an easy
to use script or a `make` rule to generate these maintainer-scripts from these
templates?
Many thanks
Morgwai
