[SRU][M,J,F][PATCH v2] Cranky update-dkms-versions rollout

Roxana Nicolescu roxana.nicolescu at canonical.com
Mon Mar 4 09:33:45 UTC 2024


BugLink: https://bugs.launchpad.net/bugs/2055685

SRU Justification

[Impact]
Having a common file for dkms-versions between main kernels and
derivatives causes a lot of conflicts during rebase.
Solution is to have a dkms-versions per kernels, under
debian.<derivative>/dkms-version.

While at it, instead of running ./update-dkms-version script, cranky
update-dkms-versions was introduced.

[Fix]
This is needed only in the main kernels.
1. remove update-dkms-version script
2. rename debian/dkms-version with debian.master/dkms-versions
3. Replace debian/dkms-versions references in debian scripts and rules
with $(DEBIAN)/dkms-versions
The 3rd fix required separate patches because the scripts are a bit
different.
4. Remove update-version-dkms since it's an old script and not being
used anymore.

Note for derivatives: These changes will be inherited from the parent
during cranky rebase.
The only change to the cranky process is: instead of using
./update-dkms-versions
script, cranky-update-dkms-versions should be used

[Test]
Build test on cbd. No issue found.

[Regression pottential]
Owners have tried this last cycle in derivatives and no issues were
found.
We may see build failures due to wrong dkms versions, but it will be
fixed along the way.

Changes since v2:
Removed update-versions-dkms for focal and jammy. Mantic did not have
it. This script is old and not used anymore.

-- 
2.34.1




More information about the kernel-team mailing list