#575183 suggests that it would be useful to know which hypervisor was
installed when reportbug is used to report a bug against the kernel.
Any objection to adding "xen-hypervisor" to
linux-2.6/debian/templates/image.plain.bug/control? It seems from a
quick test that this follow dependencies and generates what seems to be
the right thing to me e.g
Versions of packages linux-image-2.6.32-3-xen-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
ii firmware-ivtv 0.23 Binary firmware for iTVC15-family
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
ii firmware-linux-nonfree 0.23 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
ii xen-hypervisor-3.4-amd64 [xe 3.4.3~rc3-1 The Xen Hypervisor on AMD64
Given that I would like to make changes in both trunk and the sid branch
is there a normal procedure there or should I just make equivalent
commits in both places?
I was also thinking it might also be useful to include the output of "ls
-lRt /boot" and/or /boot/grub/{grub.cfg,menu.lst}/other-bootloader-cfgs
via one of the report bug hooks. I was wondering if that had been
considered and rejected for some reason (privacy issues perhaps?) I
guess perhaps the bootloader config thing might be appropriately handled
by having bootloader packages drop some control info in "the right
place" (whatever that might be).
Ian.
--
Ian Campbell
"In matters of principle, stand like a rock; in matters of taste, swim with
the current."
-- Thomas Jefferson
Attachment:
signature.asc
Description: This is a digitally signed message part