Jeroen van Wolffelaar wrote: > 2) How should it be resolved? > - Personal favourite, make this package arch:any, and have per architecture > the needed boot loader for that architecture.
I don't see any problem with making the debian-edu package arch any, although I've not tried to build it anywhere except i386. I think it should work with no or only small changes, the existing build system should notice grub is not available and drop it from the recommends if built on other arches. And another good argument for making it arch any is that we want the same package be available on i386 (grub, mdetect, read-edid, etc recommendations included) even if someone uploads a new version built on some other arch. Currently such an upload would drop packages not available on that arch from the packages available for i386. This package does require access to a debian mirror to build, which could potentially be a problem on some autobuilders. -- see shy jo
signature.asc
Description: Digital signature
