Package: qemu
Version: 0.10.6-1
Severity: important
qemu ships copies of etherboot roms by build-depending on etherboot, and
copying the binaries from the etherboot package into the generated qemu
package. this makes it difficult to track the actual sources where the
etherboot roms come from.
from debian/rules:
zcat /usr/share/etherboot/e1000-82540em.zrom.gz >
$(CURDIR)/debian/tmp/usr/share/qemu/pxe-e1000.bin
zcat /usr/share/etherboot/rtl8029.zrom.gz >
$(CURDIR)/debian/tmp/usr/share/qemu/pxe-ne2k_pci.bin
zcat /usr/share/etherboot/pcnet32.zrom.gz >
$(CURDIR)/debian/tmp/usr/share/qemu/pxe-pcnet.bin
zcat /usr/share/etherboot/rtl8139.zrom.gz >
$(CURDIR)/debian/tmp/usr/share/qemu/pxe-rtl8139.bin
i reported a wishlist bug on etherboot (#552402) to generate a separate package
with these roms, which would be an ideal way to solve this.
alternately, qemu could recommend etherboot and gunzip the appropriate roms
somewhere (/var/cache?) during package installation, though these could get out
of sync with the installed etherboot versions, and pulls in a very large
dependency.
getting gPXE (the next generation of etherboot) packaged in debian (ITP:
#474034) with a package that only includes the roms appropriate to qemu would
be another option (and support virtio-net as well).
live well,
vagrant
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
