Control: reassign -1 src:debian-installer 20120828 , grub-common 1.99-27
Control: tags -1 -moreinfo
Control: affects -1 +debian-installer-7.0-netboot-kfreebsd-i386
Control: affects -1 +debian-installer-7.0-netboot-kfreebsd-amd64
Hi all,
I spent some more time debugging this RC bug by setting up my server and
testing the PXE boot of kfreebsd-i386 on two different laptops; the
results are:
* the "error: prefix is not set" error always appears when using the
wheezy grub2pxe; it also happens with the current sid grub2pxe [0];
* the resistance to this error apparently depends on the PXE
implementation:
- my "acer Aspire One" displays the error and then proceeds to
displaying grub, then allowing the boot of the kfreebsd-i386
installer;
- my "ThinkPad X220" displays the error and stops;
- kvm launched locally with [1] proceeds to grub;
[0] http://http.debian.net/debian/dists/sid/main/installer-kfreebsd-i386/20130430/images/netboot/grub2pxe
[1] kvm -m 256 -net nic -net -
user,bootfile=/grub2pxe,tftp=/usr/lib/debian-installer/images/7.0/kfreebsd-amd64/gtk/
As debian-installer-netboot-images is only copying these files from the
mirrors, I don't think it is the correct source package to track this
bug. The above tests now make me think that this is either a problem of
debian-installer calling grub-mkimage wrongly in
build/config/kfreebsd.cfg or a bug in grub-mkimage not incorporating the
prefix correctly when creating a PXE image. I'm therefore hereby
reassigning this bug to both these packages (in their wheezy versions)
and marking it as affecting the correct d-i-n-i binary packages.
Cheers,
OdyX
Attachment:
signature.asc
Description: This is a digitally signed message part.