This is now fixed upstream
https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/83
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
grub-install command line options incompatible
The attachment "This patch is against the vmdb2-0.19 upstream tag" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
** Patch added: "This patch is against the vmdb2-0.19 upstream tag"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+attachment/5453052/+files/0001-Support-grub-compat-setting-for-Ubuntu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've sent a patch to
https://gitlab.com/larswirzenius/vmdb2/-/issues/36#note_485816538 which
enables support for Ubuntu and Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
This also keeps me from using vmdb2 to build a custom Ubuntu image. FWIW
I opened https://gitlab.com/larswirzenius/vmdb2/-/issues/36 to discuss
fixing this from the vmdb2 side instead, which might be an alternative
solution.
** Bug watch added: gitlab.com/larswirzenius/vmdb2/-/issues #36
Hello,
FWIW this breaks the vmdb2 on Ubuntu ("grub: uefi" steps break), and
makes it impossible to build uefi bootable Ubuntu images. It would be
great to get his merged as a noop, perhaps it would best if the output
warned that this is a deprecated flag and is a noop, to discourage its
future
Thanks.
I think I'm basically OK with the idea of this patch, but I'd want to
see it in isolation rather than needing to dig through the whole Ubuntu
delta for it. Maybe I could have a merge request or something?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
I have an issue with leaving cruft around instead of actively fixing
whatever depends on old behavior; months from now, or even years, we'll
still have this switch around that does nothing -- that's more confusing
for users than actively moving forward.
That said, I'll defer to Colin and add the
As the Debian maintainer, I entirely disagree. Even though it's now the
default behaviour, --force-extra-removable should be kept as a no-op,
because it's used by other software. Interfaces matter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(To be clear, I disagree with Mathieu and agree with Antonio.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
grub-install command line options incompatible with Debian
To manage
I disagree. This needs to be fixed in Debian as well -- none of the
options are crazy hacks, they are taken as explicit decisions meant to
fix actual problems that people are having.
I have to rebase the patches for Debian, sure; but I don't think we
should leave breadcrumbs around because a test
12 matches
Mail list logo
