On Fri, Jan 09, 2009 at 08:04:57PM -0000, Paul Taylor wrote: > First, is this a legitimate possibility?
Yes, it is. > Even if it is, could it be eliminated by generating a dummy initramfs, even > where it is not needed No, because the entire problem is that update-grub is being called (for a reason that I presume is legitimate) before the kernel postinst has a chance to do its job, and then kernel package installation is somehow failing to call update-grub afterwards. So the only reliable point at which we would generate the dummy initramfs is the same point at which we generate the real one. > Finally, I noticed from a search of lauchpad that there have actually been > lots of reports of this bug, dating back to 2006. It is probable that most of these are false-positives due to broken configurations (/etc/kernel-img.conf) or other bugs that have already been fixed. For that matter, the bug you describe is not the same as the one originally reported by psl and confirmed by Ante; conflating the two issues in a single bug report makes it harder to get to the root of either bug. The ubiquity bug really should have been opened as a separate bug report. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
