[Bug 1997779] Re: grub2-signed postinsts need to source debconf

[Launchpad Bug Tracker]

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 <juliank at ubuntu.com>  Thu, 01 Dec 2022 17:13:46
+0100

** Changed in: grub2-signed (Ubuntu Lunar)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1997779

Title:
  grub2-signed postinsts need to source debconf

Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2-signed source package in Focal:
  Triaged
Status in grub2-signed source package in Jammy:
  Triaged
Status in grub2-signed source package in Kinetic:
  Triaged
Status in grub2-signed source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  dpkg-reconfigure grub-efi-*-signed do nothing, as debconf is weird and sourcing the script inside grub-multi-install is not enough.

  This means the questions about which ESP(s) to use might not get
  asked.

  [Test plan]
  Run dpkg-reconfigure grub-efi-amd64-signed, ensure it shows debconf prompts.

  same for grub-efi-arm64-signed

  [Where problems could occur]
  I'm not sure where problems could occur from adding a single line to the top of postinst that sources debconf when all other packages have it too, hmm.

  But of course debconf is always a bit weird. Maybe questions get asked
  twice, I don't know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1997779/+subscriptions