This bug was fixed in the package linux - 5.8.0-36.40+21.04.1

---------------
linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium

  * Packaging resync (LP: #1786013)
    - update dkms package versions

  [ Ubuntu: 5.8.0-36.40 ]

  * debian/scripts/file-downloader does not handle positive failures correctly
    (LP: #1878897)
    - [Packaging] file-downloader not handling positive failures correctly

  [ Ubuntu: 5.8.0-35.39 ]

  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * CVE-2021-1052 // CVE-2021-1053
    - [Packaging] NVIDIA -- Add the NVIDIA 460 driver

 -- Kleber Sacilotto de Souza <kleber.so...@canonical.com>  Thu, 07 Jan
2021 11:57:30 +0100

** Changed in: linux (Ubuntu Hirsute)
       Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1902957

Title:
  Update kernel packaging to support forward porting kernels

Status in linux package in Ubuntu:
  Fix Released
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 Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

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/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to