This bug was fixed in the package linux-restricted-modules-oem-6.1 -
6.1.0-1023.23+3
---------------
linux-restricted-modules-oem-6.1 (6.1.0-1023.23+3) jammy; urgency=medium
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (adhoc/2023.09.04)
-- Andy Whitcroft <a...@canonical.com> Wed, 27 Sep 2023 10:55:17 +0100
** Changed in: linux-restricted-modules-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux-meta-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2019024
Title:
Migrate oem-5.17 and oem-6.0 to oem-6.1
Status in linux-meta-oem-6.1 package in Ubuntu:
Invalid
Status in linux-restricted-modules-oem-6.1 package in Ubuntu:
Invalid
Status in linux-meta-oem-6.1 source package in Jammy:
Fix Released
Status in linux-restricted-modules-oem-6.1 source package in Jammy:
Fix Released
Bug description:
[Impact]
Migrate oem-5.17 and oem-6.0 to oem-6.1 now that there should be no
functional regressions left anymore.
[Test case]
Update a machine with oem-5.17/oem-6.0 metapackages to the proposed ones, and
verify that all packages (including nvidia etc) migrate properly.
[Where things could go wrong]
In theory we might miss a package to transition, but at this point this is
unlikely.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2019024/+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
