** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-aws-fips 
verification-needed-jammy-linux-nvidia-tegra verification-needed-xenial-linux
** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra verification-done-xenial-linux

** Tags removed: verification-needed-bionic-linux 
verification-needed-focal-linux-aws-5.15
** Tags added: verification-done-bionic-linux 
verification-done-focal-linux-aws-5.15

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  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. This is not used in xenial,
  therefore for xenial we only replaced debian/dkms-versions with
  debian.<derivative>/dkms-versions

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script (where needed), in xenial:linux we don't 
have it
  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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to