vcswatch reports that
this package seems to have a new changelog entry (version
2.04-4, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit c07e884597c085c518ce8e8a02cc3309b5c4b98f
Merge: f2d317f1 2e37e926
Author: Colin Watson <cjwatson@debian.org>
Date: Sat Aug 31 22:34:07 2019 +0100
Merge remote-tracking branch 'salsa/merge-requests/13/head'
commit 2e37e926cca551cd50485c6ef30a3b0b1f9469d7
Author: Thomas Gaugler <thomas@dadie.net>
Date: Sat Aug 31 17:58:55 2019 +0200
Add leading / to prefix of network boot image for d-i
The win32-loader package relies on the hosted netboot debian-installer
files.
The grubx64.efi file is located at
https://deb.deb.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/gtk/debian-installer/amd64/grubx64.efi
and originates from the grub2 source package.
This grubx64.efi file includes the preconfigured prefix:
($root)debian-installer/amd64/grub.
This prefix lacks the leading / in front of debian-installer. Therefore
no grub.cfg file located on a local storage device can be accessed via
this preconfigured prefix.
The normal network boot image uses ($root)/grub as its prefix. As a
stopgap the win32-loader package (experimental) transforms the above
mentioned grubx64.efi file into a normal network boot image (also known
as grubnetx64.efi.signed of the grub-efi-amd64-signed_1+2.02+dfsg1+20
package). As a consequence the grub.cfg file could be accessed at the
($root)/grub prefix.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/grub2.png){kind=link}