[Impact]
Users upgrading from jammy to mantic will not have an mstflint-dkms package. This will leave the mstflint-dkms package from jammy installed, which is incompatible with the 6.5 kernel.
[Test Case]
mstflint-dkms installs in mantic and builds against the mantic kernel. Also, mstflint-dkms/mantic upgrades cleanly from jammy.
Regression test: compare the contents of the mstflint binary package before/after, makes sure the file list matches and maintainer scripts are equivalent.
[What Could Go Wrong]
Introducing the mstflint-dkms package should carry a low regression risk because the package does not already exist in mantic. However, the packaging changes could introduce regressions in the other binary package, mstflint, if they are buggy.
[Impact]
Users upgrading from jammy to mantic will not have an mstflint-dkms package. This will leave the mstflint-dkms package from jammy installed, which is incompatible with the 6.5 kernel.
The reason we ended up here was due to a bypass of the SRU process, described here: /bugs.launchpad .net/ubuntu/ +source/ mstflint/ +bug/2051571/ comments/ 1
https:/
[Test Case] dkms/mantic upgrades cleanly from jammy.
mstflint-dkms installs in mantic and builds against the mantic kernel. Also, mstflint-
Regression test: compare the contents of the mstflint binary package before/after, makes sure the file list matches and maintainer scripts are equivalent.
[What Could Go Wrong]
Introducing the mstflint-dkms package should carry a low regression risk because the package does not already exist in mantic. However, the packaging changes could introduce regressions in the other binary package, mstflint, if they are buggy.