Bug#981819: grub2: Add grub-efi dummy package on all supported architectures

[Colin Watson]

On Thu, Feb 04, 2021 at 11:17:48AM +0100, Raphael Hertzog wrote:
> Tools like simple-cdd ensures the presence of grub-efi on the generated
> ISO image but don't have a simple way to to deal with architecture
> specific packages.
> 
> When we tested an arm64 image generated by simple-cdd, it was lacking the
> grub-efi support and thus the installer was broken.
> 
> Thus I'd like to suggest to keep grub-efi not as a transitional package
> but as normal dummy package depending on the appropriate package for
> each architecture.
[...]
>  Package: grub-efi
> -Section: oldlibs
> -Architecture: any-i386 any-amd64
> +Architecture: any-i386 any-amd64 any-arm64 any-ia64 any-arm
>  Pre-Depends: ${misc:Pre-Depends}
> -Depends: ${misc:Depends}, grub-efi-ia32 (= ${binary:Version}) [any-i386], grub-efi-amd64 (= ${binary:Version}) [any-amd64]
> +Depends: ${misc:Depends}, grub-efi-ia32 (= ${binary:Version}) [any-i386], grub-efi-amd64 (= ${binary:Version}) [any-amd64], grub-efi-arm64 (= ${binary:Version}) [any-arm64], grub-efi-ia64 (= ${binary:Version}) [any-ia64], grub-efi-arm (= ${binary:Version}) [any-arm]
>  Multi-Arch: foreign
>  Description: GRand Unified Bootloader, version 2 (dummy package)
> - This is a dummy transitional package that depends on either grub-efi-ia32 or
> - grub-efi-amd64, depending on the architecture.
> -
> + This is a dummy package that depends on the appropriate grub-efi-$ARCH
> + for each architecture:
> +  - grub-efi-amd64 on amd64
> +  - grub-efi-ia32 on i386
> +  - grub-efi-arm64 on arm64
> +  - grub-efi-ia64 on ia64
> +  - grub-efi-arm on arm

The reason we made grub-efi into a transitional package in the first
place is that this simple mapping between userspace and firmware doesn't
always hold: for example, if you're running i386 userspace on x86
hardware with 64-bit firmware, you have to use grub-efi-amd64.

How about instead writing "... on the grub-efi-$ARCH package most likely
to be appropriate for each architecture", and dropping the detailed list
from the description that really just recapitulates the Depends field?
I think I'd be OK with that, and then it would be less misleading while
still meeting your needs in most cases.

-- 
Colin Watson (he/him)                              [cjwatson at debian.org]