** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed -- 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/1902957 Title: Update kernel packaging to support forward porting kernels Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed 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 Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact: Our kernel packaging currently has support for backporting kernels to older releases. This includes appending ~BACKPORT_SUFFIX to the version string for the backport kernel, where BACKPORT_SUFFIX is defined in update.conf. We need to start doing similar forward ported kernels, but BACKPORT_SUFFIX should be appended using a + rather than a ~. Our kernel packaging cannot easily determine whether a + or a ~ is appropriate. Fix: Move the leading character into BACKPORT_SUFFIX, and do not insert any leading characters from the kernel packaging scripts. Since the script which generates update.conf has access to information from kernel-series, it can more easily determine whether + or ~ is the appropriate leader. Test Case: Run through the normal steps for updating a backport kernel. The version string generated should have ~SERIES for a backport to an older series, and +SERIES for a backport to a newer series. Regression Potential: Backport kernels could end up with an incorrect version strings. Since all kernel uploads undergo review, any such errors should be caught before uploading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902957/+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