Comment 2 for bug 1611740

On Wed, Aug 10, 2016 at 01:33:34PM -0000, Mathieu Trudel-Lapierre wrote:
> Looks like we only install grub (legacy) if we're about to install grub-
> pc and "grub-installer/grub2_instead_of_grub_legacy" is preseeded to
> false, which typically doesn't happen. It's default is true, and we
> don't set this in ubiquity or d-i.

> grub-legacy-ec2 installs some data for EC2 instances that is relevant to
> grub; we should definitely look at how we'd affect it by removing grub
> (but I think it's safe there)

> The open question that remains is handling upgrades.

grub (0.97-29ubuntu68) xenial; urgency=medium

  * No-change rebuild for ncurses6 transition.

 -- Matthias Klose <email address hidden> Sun, 07 Feb 2016 09:41:39 +0000

grub (0.97-29ubuntu67) wily; urgency=medium

  * Port to modern Automake versions and use dh-autoreconf (closes:
    #724383).
  * Build with -fno-combine-stack-adjustments, since that optimisation pass
    confuses the stack games played by GRUB itself (closes: #768135).
  * Stop linking statically on amd64, which was a holdover from a long time
    ago when we couldn't just depend on biarch libraries (closes: #769349).

 -- Colin Watson <email address hidden> Mon, 05 Oct 2015 13:52:39 +0100

grub (0.97-29ubuntu66) precise; urgency=low

<snip>

There have been only two uploads of the grub package since the release of
the oldest supported LTS (4 years ago). It stopped being a default
bootloader longer ago than that. We should be honest with ourselves
that we're never going to take the time to finish automated upgrade support
for grub->grub2 and just drop the package.

We should definitely fix grub-installer to not try to install a non-existent
grub package from the archive, with or without preseed.