Comment 27 for bug 1696154

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-signed - 4.15.0-19.20

---------------
linux-signed (4.15.0-19.20) bionic; urgency=medium

  * Master version: 4.15.0-19.20

linux-signed (4.15.0-18.19+signed2) bionic; urgency=medium

  * Fix dbgsym package handling to work for the case where we have a
    bumped linux-signed version number.

linux-signed (4.15.0-18.19+signed1) bionic; urgency=medium

  * Fix the dbgsym packages to be correctly named as .ddeb instead of .deb
    so they are published to the right archive.

linux-signed (4.15.0-18.19) bionic; urgency=medium

  * Master version: 4.15.0-18.19

  * signing: only install a signed kernel (LP: #1764794)
    - switch to raw-signing tarball form
    - make control.stub master for packages built
    - [Config] tone down the output verbosity
    - switch to producing linux-image directly
    - propogate control information from -unsigned package
    - pull control files in from linux-unsigned
    - resync control files with master
    - introduce meta packages for the debug package
    - fix names of substvars files
    - propogate Recommends: and Provides: from unsigned package
    - fix Section: control records
    - do not produce lowlatency dbgsym package for ppc64el
    - move dbgsym packages to bottom of control file
    - ensure we apt-cache show against the exact version

  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
    - add Opal signing support and enable for ppc64el

linux-signed (4.15.0-17.18) bionic; urgency=medium

  * Master version: 4.15.0-17.18

linux-signed (4.15.0-16.17) bionic; urgency=medium

  * Master version: 4.15.0-16.17

 -- Seth Forshee <email address hidden> Sat, 21 Apr 2018 17:32:56 -0500