** Summary changed:

- Migrate oem-5.17 to oem-6.1
+ Migrate oem-5.17 and oem-6.0 to oem-6.1

** Description changed:

  [Impact]
- Migrate oem-5.17 to oem-6.1 now that there should be no functional 
regressions left anymore.
+ 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 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.
+ 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.

-- 
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:
  New
Status in linux-restricted-modules-oem-6.1 source package in Jammy:
  New

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

Reply via email to