On Friday 20 November 2009 08:15:34 sriva...@acm.org wrote: > > This is not really a critical bug. It is only triggered when > the user asks for a XEN dom0 image, and is using grub2, and has not > told grub2 to ignore vmlinux. > > In any case, 12.030 will not ship vmlinux unless asked. > > I think there is a mismatch between our expectations; I expect > people compiling kernels to be aware of their configuration, and to > have set the configuration according to their desires. In this case, > a dom0 image is being asked for; and you are hitting a flux in > kernel-package's treatment of XEN images. > > This is not encountered with the standard (that is, make > defconfig) configurations.
I repeat, I am not doing anything "non-standard": $ cp /boot/config-2.6.31-1-amd64 .config $ make-kpkg --initrd --revision=custom.1.2 kernel_image *I* did not ask for XEN, this is part of the debian stock kernel image configuration. *I* did not instruct grub2 not to ignore vmlinux, my grub2 configuration was installed as standard. Until the recent change, I had never seen vmlinux, and therefore there was no problem. Why was the decision made to now produce this? Also, I can find no mention of "make defconfig" in /usr/share/doc/kernel-package/README.gz so please do not moralize me and recognize that there IS a bug! Sincerely, Alan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
