This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-failed-jammy-linux-xilinx-zynqmp'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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 Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
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
Комментариев нет:
Отправить комментарий