Bug#545292: grub-pc: upgrade from grub1: kopt question is ambigious and confusing

[Jon Dowland]

Package: grub-pc
Severity: normal

Installing grub-pc and I receive the following debconf
prompt:

 │ The following Linux command line was extracted from /etc/default/grub or  │ 
 │ the `kopt' parameter in GRUB Legacy's menu.lst.  Please verify that it    │ 
 │ is correct, and modify it if necessary.                                   │ 
 │                                                                           │ 
 │ Linux command line:                                                       │ 
 │                                                                           │ 
 │ _________________________________________________________________________ │

(note, that is, the command line is blank).

My kopt line is

# kopt=root=/dev/mapper/tchicaya_vg1-root ro

I'm guessing (after reading some other bug reports) that
what grub-pc is trying to determine is any *other* command
line arguments, besides the root device and 'ro'. This
isn't clear, and my first reaction was "it's missing
root=blah and ro, that won't work!"

Adjusting the text to make clear that it doesn't need the
root device nor ro would avoid some confusion. (Unless I'm
mistaken and it *does* need these, and has failed to parse
them somehow...)

Finally in the case where no other kopts are detected (as
above) the prompt might make more sense worded "grub-pc did
not detect and kernel command-line options in your old GRUB
configuration. If any options are required, aside from the
root device and 'ro', please enter them here:"

-- System Information:
Debian Release: squeeze/sid
  APT prefers transitional
  APT policy: (500, 'transitional'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash