Yay! It only took 7 years ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611740
Title:
remove grub, superseded by grub2
To manage notifications about this bug go to:
Removing packages from zesty:
grub 0.97-29ubuntu69 in zesty
grub 0.97-29ubuntu69 in zesty amd64
grub 0.97-29ubuntu69 in zesty i386
grub-disk 0.97-29ubuntu69 in zesty amd64
grub-disk 0.97-29ubuntu69 in zesty arm64
I have spoken with the Canonical CPC team, and the EC2 AMIs are not
built using the grub source package; they only use the grub-legacy-ec2
package (built from cloud-init source) which provides grub1-compatible
menu.lst.
--
You received this bug notification because you are a member of Ubuntu
grub legacy support is indeed removed from grub-installer now (see above
upload comment).
However, grub is apparently still required when building new AMI
instances for EC2. I think it probably best not be removed until we can
ascertain its use. I've asked the CPC team already.
According to the
This bug was fixed in the package grub-installer - 1.128ubuntu6
---
grub-installer (1.128ubuntu6) yakkety; urgency=medium
* grub-installer: remove grub/grub-legacy code. We only do variants of grub2.
(LP: #1611740)
-- Mathieu Trudel-Lapierre Thu, 11
** Branch linked: lp:~ubuntu-core-dev/grub-installer/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611740
Title:
remove grub, superseded by grub2
To manage notifications about this bug go
I had looked anyway and the "upgrade path" appears appropriate.
Installing grub-pc will tell you how to proceed with the upgrade, in
which case you can either chainload the new grub or replace things
altogether. Seems to me like a go to remove grub.
Adding the grub-installer task to drop the
On Wed, Aug 10, 2016 at 01:33:34PM -, 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
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