grub2-signed postinsts need to source debconf

This bug was fixed in the package grub2-signed - 1.189

---------------
grub2-signed (1.189) lunar; urgency=medium

  * Really rebuild against grub2 2.06-2ubuntu15

grub2-signed (1.188) lunar; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu15
  * Source debconf in postinst script (LP: #1997779)
  * Still signed with the old key

grub2-signed (1.187) kinetic; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

 -- Julian Andres Klode <email address hidden> Thu, 01 Dec 2022 17:13:46 +0100

Hello Julian, or anyone else affected,

Accepted grub2-signed into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.173.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Both amd64 and arm64 verifications failed:

= amd64 =
ubuntu@ubuntu:~$ dpkg -l | grep grub-efi
ii grub-efi-amd64-bin 2.04-1ubuntu47.5 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii grub-efi-amd64-signed 1.173.4+2.04-1ubuntu47.5 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ubuntu@ubuntu:~$ sudo dpkg-reconfigure grub-efi-amd64-signed
Unknown device "/dev/disk/by-id/*": No such file or directory
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
Installation finished. No error reported.
ubuntu@ubuntu:~$ sudo dpkg-reconfigure grub-efi-amd64-signed -plow
Unknown device "/dev/disk/by-id/*": No such file or directory
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
Installation finished. No error reported.
ubuntu@ubuntu:~$

= arm64 =
ubuntu@ubuntu:~$ sudo dpkg-reconfigure grub-efi-arm64-signed -plow
Unknown device "/dev/disk/by-id/*": No such file or directory
Installing grub to /boot/efi.
Installing for arm64-efi platform.
Installation finished. No error reported.
ubuntu@ubuntu:~$ dpkg -l | grep grub-efi-arm64-signed
ii grub-efi-arm64-signed 1.173.4+2.04-1ubuntu47.5 arm64 GRand Uni
fied Bootloader, version 2 (EFI-ARM64 version, signed)

Ugh, gotta double check what's going on there. It's possible we miss some test instructions, like unmount /boot/efi or something

The problem in the verification above was:

> Unknown device "/dev/disk/by-id/*": No such file or directory

aka we don't support virtio-blk in the debconf, because those don't have by-id. That's tracked in bug 1997797 (yes confusingly similar number).

I reran this using

$ multipass launch focal

Then in there checked dpkg-reconfigure did nothing, then upgraded to the 47.5 version:

Unpacking grub-efi-amd64-signed (1.173.4+2.04-1ubuntu47.5) over (1.173.2~20.04.1+2.04-1ubuntu47.4) ...

After that, dpkg-reconfigure prompted me correctly.

This bug was fixed in the package grub2-signed - 1.173.4

---------------
grub2-signed (1.173.4) focal; urgency=medium

  * Source debconf in postinst script (LP: #1997779)
  * Enforce build against 2.04-1ubuntu47.5

grub2-signed (1.173.3) focal; urgency=medium

  * Rebuild against grub2 2.04-1ubuntu47.5 (LP: #1996950)
  * Bump grub2-common dependency to 2.02~beta2-36ubuntu3.33 in xenial and
    2.02-2ubuntu8.25 in bionic to fix LP: #1995751

 -- Julian Andres Klode <email address hidden> Fri, 02 Dec 2022 15:15:54 +0100

The verification of the Stable Release Update for grub2-signed has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Verified for the 2.06 focal update too.

For some reason the SRU tooling did not do the verification-needed bits for any release, but I marked it verified for bionic. We do not actually have support for this in bionic, so this doesn't do anything of course, the bug is just listed in the changelog due to copying the package verbatim.

So I just tested that it installed successfully and rebooted in multipass.

Verified for jammy 1.187.2+2.06-2ubuntu14 in multipass.

Verified for kinetic 1.187.2+2.06-2ubuntu14 in multipass

This bug was fixed in the package grub2-signed - 1.187.2

---------------
grub2-signed (1.187.2) kinetic; urgency=medium

  * Resign with 2022v1 signing key

grub2-signed (1.187.1) kinetic; urgency=medium

  * Source debconf in postinst script (LP: #1997779)
  * Really rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

grub2-signed (1.187) kinetic; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

 -- Julian Andres Klode <email address hidden> Mon, 09 Jan 2023 17:22:33 +0100

This bug was fixed in the package grub2-signed - 1.187.2~20.04.2

---------------
grub2-signed (1.187.2~20.04.2) focal; urgency=medium

  * Resign with 2022v1 signing key
  * [focal/bionic] remaining backport changes:
    - Bump grub2-common dependency to 2.02~beta2-36ubuntu3.33 in xenial and
      2.02-2ubuntu8.25 in bionic to fix LP #1995751

grub2-signed (1.187.1) kinetic; urgency=medium

  * Source debconf in postinst script (LP: #1997779)
  * Really rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

grub2-signed (1.187) kinetic; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

 -- Julian Andres Klode <email address hidden> Tue, 17 Jan 2023 15:51:22 +0100

This bug was fixed in the package grub2-signed - 1.187.2~18.04.1

---------------
grub2-signed (1.187.2~18.04.1) bionic; urgency=medium

  * Resign with 2022v1 signing key
  * [focal/bionic] remaining backport changes:
    - Bump grub2-common dependency to 2.02~beta2-36ubuntu3.33 in xenial and
      2.02-2ubuntu8.25 in bionic to fix LP #1995751

grub2-signed (1.187.1) kinetic; urgency=medium

  * Source debconf in postinst script (LP: #1997779)
  * Really rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

grub2-signed (1.187) kinetic; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu14 (LP: #1996950)

 -- Julian Andres Klode <email address hidden> Tue, 17 Jan 2023 15:51:22 +0100