On 02/07/2013 08:12 AM, Michael Biebl wrote:
This list is getting longer with each email. Seeing that syslinux 5 has been in sid for less then 10 days, I'm worried what other issues might show up.
apart from the two obvious things (debian-installer and debian-cd) that do need to be updated to copy in the additionally required c32 modules when using vesamenu.c32, there's only vbox broken.
while i can see that one is inclined to jump to the conclusion that now each and every package in debian needs an update, it really isn't so.
no package is directly interacting with a bootloader, except those that create images (debian-installer, debian-cd), or boot images *and* have bugs fixed-upstream-long-time-ago-but-not-in-debian (vbox).
again, note that any other virtualization software, be it in wheezy directly (qemu, kvm) or otherwise (parallels, vmware) which i've tested with, has no bugs with syslinux 5. it's an isolated thing that vbox still has that bug in debian.
-- Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5113581b.3020...@progress-technologies.net
