Bug#265915: Should exclude .dpkg-* from kernel list

Matt Zimmerman Matt Zimmerman <mdz@debian.org>, 265915@bugs.debian.org
Mon, 16 Aug 2004 00:54:20 -0700


On Mon, Aug 16, 2004 at 12:49:29AM +0200, Robert Millan wrote:

> On Sun, Aug 15, 2004 at 10:45:54AM -0700, Matt Zimmerman wrote:
> > Package: grub
> > Version: 0.95+cvs20040624-7
> > Severity: normal
> > 
> > I just saw this happen, when upgrading a kernel-image package to a new
> > version:
> > 
> > Unpacking replacement kernel-image-2.6.7-1-386 ...
> > Searching for GRUB installation directory ... found: /boot/grub .
> > Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
> > Found kernel: /boot/vmlinuz-2.6.7-1-386
> > Found kernel: /boot/vmlinuz-2.6.7-1-386.dpkg-tmp
> > Updating /boot/grub/menu.lst ... done
> > 
> > The .dpkg-tmp file is a temporary dpkg file which existed only during the
> > upgrade.  I suggest excluding .dpkg-* (at least) from the list.
> 
> The package that appear to be failing is kernel-image-foo.  What does its
> postinst do?

It's a stock 2.6.7 kernel-image, and I have the following configuration:

mizar:[~] cat /etc/kernel-img.conf
link_in_boot = yes
relative_links = yes
postinst_hook = /sbin/update-grub
postrm_hook = /sbin/update-grub
do_bootloader = no
do_initrd = yes

-- 
 - mdz