Package: elilo Version: 3.6-2 Severity: normal When elilo is updated on a system, the new elilo.efi is not automatically installed into the efi partition. The new elilo.efi binary will not be used until something triggers its installation (i.e., /usr/sbin/elilo is called, like during a kernel postinst).
This could solve a potential sarge->etch upgrade problem. If the etch linux-image is configured before elilo is upgraded, the old elilo will end up in the efi partition. sarge's elilo.efi cannot deal with initramfs, and the new linux-images require it. This would leave the system unbootable. This happened to me this evening when I installed the etch kernel onto a sarge system using various backports. Another possible solution is to add a versioned dependency on the new elilo to linux-image. Today, however, elilo is just a suggests. I'm filing this with normal severity because I don't know if this is likely to occur in a real upgrade scenario. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-itanium Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages elilo depends on: ii dosfstools 2.11-2.1 Utilities to create and check MS-D ii efibootmgr 0.5.3-2 Interact with the EFI Boot Manager elilo recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
