Bug#908200: grub-efi-*-signed: mismatch between /EFI/vendor (used) and /EFI/debian (expected) when derivative uses unmodified Debian binary packages

[Luca Boccassi]

On Fri, 7 Sep 2018 15:57:48 +0200 Raphael Hertzog <hertzog at debian.org>
wrote:
> Control: tags -1 + patch
> 
> On Fri, 07 Sep 2018, Raphaël Hertzog wrote:
> > The problem seems to come down to the fact that during initial
installation,
> > (at least) when the install picks the new *-signed packages, they
get
> > installed to /EFI/kali but the binary installed inside is actually
> > expecting the configuration file in /EFI/debian/grub.cfg.
> 
> I'm attaching a possible patch. I checked that the package builds,
but I
> did not test the resulting package.
> 
> Since the EFI image hardcodes the patch in the EFI partition, I
modified
> /etc/default/grub to contain GRUB_BOOTLOADER_ID initialized with the
> value of SB_EFI_VENDOR coming from debian/rules. grub-install has
been
> patched to initialize the default value of its --bootloader-id
parameter
> with this variable.
> 
> I opted to not modify GRUB_DISTRIBUTOR since this contains the
> user-visible name of the derivative and we want to keep that
obviously.
> 
> Cheers,
> 
> PS: I pushed my branch here too: https://salsa.debian.org/hertzog/gru
b

Hi Raphael,

Maybe the changes could be simplified a bit by using the Efi-Vendor
package metadata that was added in the same version?
Something like this might work:

dpkg-query -f='${Efi-Vendor}' -W @PACKAGE at -bin

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20180921/9424d9d8/attachment.sig>