Bug#425056: strange default for link_in_boot in config script

[Ralf Neubauer <ralf@strcmp.de>]

I have the same problem with linux-image-2.6.21-2-686

In /var/lib/dpkg/info/linux-image-2.6.21-2-686.config I found the
suspicious lines

# Predefined values:
my $version           = "2.6.21-2-686";
my $link_in_boot      = "YESB";   # Should be empty, mostly
my $no_symlink        = "";   # Should be empty, mostly
my $reverse_symlink   = "";   # Should be empty, mostly
my $do_symlink        = "Yes";  # target machine defined
my $do_boot_enable    = "Yes";  # target machine defined

linux-image-2.6.18-5-686.config still contains

# Predefined values:
my $version           = "2.6.18-5-686";
my $link_in_boot      = "";   # Should be empty, mostly
my $no_symlink        = "";   # Should be empty, mostly
my $reverse_symlink   = "";   # Should be empty, mostly
my $do_symlink        = "Yes";  # target machine defined
my $do_boot_enable    = "Yes";  # target machine defined

kernel-img.conf(5) (from etch) says

       link_in_boot
              Set to Yes if you want the symbolic link to  the  kernel image,
              namely,  vmlinuz  in  /boot rather than the default /.  The old,
              and very confusing, name image_in_boot is deprecated, since  it
              is  the symbolic link that is usually being relocated.  Defaults
              to No.

Has the default changed? I can't image a reason for doing this, as
only people still using lilo should be affected at all. There was no
mention of a changed default in any changelog or NEWS I searched.

Is this a kernel-package bug?

-- 
00000000  72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a     ralf@strcmp.de.