Bug#858832: calls efibootmgr with invalid options

[Steve McIntyre]

Hi!

On Mon, Mar 27, 2017 at 12:24:16PM +0000, Peter Palfrader wrote:
>Package: grub-efi-arm64
>Version: 2.02~beta3-5
>Severity: serious
>User: debian-admin at lists.debian.org
>Usertags: needed-by-DSA-Team
>
>On upgrading from jessie to stretch on our arm64 box acker.debian.org I
>noticed this issue with grub-efi-arm64:
>
>acker:~# apt-get install --reinstall grub-efi-arm64
>Reading package lists... Done
>Building dependency tree       
>Reading state information... Done
>0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
>Need to get 73.0 kB of archives.
>After this operation, 0 B of additional disk space will be used.
>Get:1 http://mirror.netcologne.de/debian stretch/main arm64 grub-efi-arm64 arm64 2.02~beta3-5 [73.0 kB]
>Fetched 73.0 kB in 0s (603 kB/s)          
>Preconfiguring packages ...
>(Reading database ... 62883 files and directories currently installed.)
>Preparing to unpack .../grub-efi-arm64_2.02~beta3-5_arm64.deb ...
>Unpacking grub-efi-arm64 (2.02~beta3-5) over (2.02~beta3-5) ...
>Setting up grub-efi-arm64 (2.02~beta3-5) ...
>Installing for arm64-efi platform.
>efibootmgr: option requires an argument -- 'd'
>efibootmgr version 14

OK, that's odd. Can you run "grub-install -v --target=arm64-efi" and
grab the output please? Curious to see exactly what the full command
line for efibootmgr is here...

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead