Comment 29 for bug 54002

Matt,

I am not trying to be dense or malevolent. I am well aware that Edgy is a development release, etc. But I am also a computer professional who has to deal with incident reports on a daily basis, so I have a quite good understanging of the issues involved. In my opinion the handling of this bug report has not been adequate.

Just to demonstrate the facts:

# env COLUMNS=120 dpkg -l grub
[...]
ii grub 0.97-11ubuntu10 GRand Unified Bootloader

# egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub
751-
752:# Update the root device to mount-by-UUID
753-kopt=$(convert_kopt_to_uuid "$kopt")

# grep -c UUID /boot/grub/menu.lst
0
# /sbin/update-grub
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.17-7-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

# grep -c UUID /boot/grub/menu.lst
3

So as you can see, even your "fixed" version silently corrupts the system.

Against the expressed intention of the system owner/administrator who changed the relevant configuration file.

Sorry, but this is simply not acceptable. Especially since upstream Debian can detect manual changes of a config file and will not change it.