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

    From Matt Zimmerman@1:229/2 to All on Sun Aug 15 20:10:09 2004
    From: [email protected]

    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.

    --
    - mdz


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Robert Millan@1:229/2 to Matt Zimmerman on Mon Aug 16 01:10:08 2004
    From: [email protected]

    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?

    --
    Robert Millan

    (Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\ (kernel of *(Berkeley Software Distribution))


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Jason Thomas@1:229/2 to Robert Millan on Mon Aug 16 01:40:08 2004
    From: [email protected]

    I've seen this too but usually the install runs update-grub twice, the
    second time this file does not exists.

    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?


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Matt Zimmerman@1:229/2 to Robert Millan on Mon Aug 16 10:10:09 2004
    From: [email protected]

    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


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)