> "linux-signed-* packages were transitional and were removed in the 5.4"
Shame we only find this out after it's done.
IRC chat with vorlon confirms that since 2019, linux-image-generic *will* have the signed bits already, this is change back through Trusty (precise does not have the right kernel bits to do this); so pending confirmation with Kernel team, but MAAS/Curtin should just use linux-image-generic.
Things to do
1) determine how long linux-signed-generic metapackage will live in previous releases (it's already gone in focal)
2) determine if other kernel varients (linux-image-lowlatency, etc) will also be signed
Curtin can change to installing linux-image-generic on focal and newer releases (in places where it would normally have used linux-signed-generic). MAAS will need to do the same if it's providing kernel-mappings (like it was in this bug).
> "linux-signed-* packages were transitional and were removed in the 5.4"
Shame we only find this out after it's done.
IRC chat with vorlon confirms that since 2019, linux-image-generic *will* have the signed bits already, this is change back through Trusty (precise does not have the right kernel bits to do this); so pending confirmation with Kernel team, but MAAS/Curtin should just use linux-image- generic.
Things to do
1) determine how long linux-signed- generic metapackage will live in previous releases (it's already gone in focal) image-lowlatenc y, etc) will also be signed
2) determine if other kernel varients (linux-
Curtin can change to installing linux-image-generic on focal and newer releases (in places where it would normally have used linux-signed- generic) . MAAS will need to do the same if it's providing kernel-mappings (like it was in this bug).