tags 973467 - patch
tags 973467 + confirmed upstream
severity 973467 important
thanks
Hello Ryutaroh,
As you said here, the workaround is not a fix, as it would make vmdb2
produce images unable to boot on amd64 - So I'm removing the "patch"
tag. I am also adding the tags "confirmed" and "upstream", as the
comments in the file in question mention:
# Note that this is currently rather strongly assuming that UEFI and
# the amd64 (a.k.a. x86_64) architecture are being used. These should
# probably not be hardcoded. Patch welcome.
I will be taking this issue with upstream author, I think the patch is
somewhat trivial, but given I lack any hardware to test it, I will not
commit a fix without his approval.
Finally, I am downgrading the severity to "important", as I judge this
bug to be "a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone"¹. It
does not completely render vmdb2 useless, not even for the arm64
architecture (for which I use it on a daily basis!) - Just for arm64
machines that boot via UEFI.
¹ https://www.debian.org/Bugs/Developer#severities
Greetings,
Ryutaroh Matsumoto dijo [Sat, Oct 31, 2020 at 02:32:27PM +0900]:
> Control: tags -1 + patch
>
> The following workaround (NOT A FIX AT ALL) let vmdb2 work for my arm64...
>
> --- usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py-orig
> 2020-10-31 12:47:04.796899268 +0900
> +++ usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py 2020-10-31
> 12:50:00.322817935 +0900
> @@ -112,8 +112,8 @@
> raise Exception('"efi" or "efi-part" required in UEFI GRUB
> installation')
>
> vmdb.progress("Installing GRUB for UEFI")
> - grub_package = "grub-efi-amd64"
> - grub_target = "x86_64-efi"
> + grub_package = "grub-efi-arm64"
> + grub_target = "arm64-efi"
> self.install_grub(values, settings, state, grub_package, grub_target)
>
> def install_bios(self, values, settings, state):
>
--
