[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

[Steve Langasek]

Bionic: server install from ubuntu-18.04.5-live-server-amd64.iso.
Security updates applied by subiquity, including grub-efi-amd64
2.04-1ubuntu44.  /etc/kernel/post{inst,rm}.d/zz-update-grub are not
present (to my surprise - then I worked out this was because grub wasn't
installed in the source squashfs, so this was a new install of the
package from -security rather than an upgrade).

grub-pc is not installed.

Enabled -proposed in sources.list.

sudo apt install grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed

/etc/kernel/post{inst,rm}.d/zz-update-grub now exist as expected

sudo apt dist-upgrade to install 4.15.0-144-generic kernel from bionic-
proposed (along with other random bits)

Inspecting /boot/grub/grub.cfg shows references to -144-.

Rebooting, and uname shows -144- is booted.

Disabled -proposed again.

sudo do-release-upgrade to focal, to my surprise, does not fail with
conffile conflicts when -proposed is disabled.  However, it does fail to
upgrade grub-efi-amd64* due to focal-updates having an earlier version
than bionic-proposed.

$ dpkg -S /etc/kernel/postinst.d/zz-update-grub
grub2-common: /etc/kernel/postinst.d/zz-update-grub
$

I do not understand what's happening here with the silent takeover of
the conffiles without an explicit Replaces allowing this; this is not
how I understood dpkg to behave.

I think this is verification-done for bionic and verification-failed for grub2 in focal (which should be withdrawn).
I do not understand what's happening with the conffile being 

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

Status in grub2 package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Invalid
Status in grub2-unsigned package in Ubuntu:
  Invalid
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  New
Status in grub2-unsigned source package in Trusty:
  Triaged
Status in grub2 source package in Xenial:
  Invalid
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in grub2-unsigned source package in Xenial:
  Fix Committed
Status in grub2 source package in Bionic:
  Invalid
Status in grub2-signed source package in Bionic:
  Fix Committed
Status in grub2-unsigned source package in Bionic:
  Fix Committed
Status in grub2 source package in Focal:
  Fix Committed
Status in grub2-signed source package in Focal:
  Fix Committed
Status in grub2-unsigned source package in Focal:
  Fix Committed
Status in grub2 source package in Groovy:
  Won't Fix
Status in grub2-signed source package in Groovy:
  Fix Committed
Status in grub2-unsigned source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on arm64
  with grub-efi-arm64 (a dependency of grub-efi-arm64-signed) installed

   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on amd64
  with grub-efi-amd64 (an ORed dependency of grub-efi-amd64-signed)
  installed.

   * This results in newly installed kernels not getting added to
  grub.cfg and thus upon reboot one does not boot into the new kernel.

   * In later series these scripts moved to grub2-common, which is why
  they are absent in the backported grub-efi-* packages.  They should be
  restored to these packages in the backport.

  [Test Plan]
   * install grub packages from -updates
   * ensure that /etc/kernel/post{inst,rm}.d/zz-update-grub are absent; if necessary, remove them
   * Install new grubs
   * If testing on amd64 ensure that grub-efi-amd64 is installed, not grub-pc.
   * Install a new kernel that was not installed before
   * Observe that grub.cfg is regenerated and new kernel is present
   * Remove an old kernel
   * Observe that grub.cfg is regenerated and new kernel is removed from grub.cfg
   * From bionic, verify that a dist-upgrade to focal works without conflicts.

  [Where problems could occur]

   * These are conffiles. Although nobody should modify them, care
  should be taken when moving conffiles around.

  [Other Info]

   * First reported by klebers

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