It seems that initramfs-tools has become confused when a kernel was removed, perhaps as a result of the initrd seeming changed from its point of view. If that happens the kernel removal can continue without it removing the state and from there it will fail to update "all" initamfs images.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/220094 Title: initramfs-tools trigger fails if modules aren't installed Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I upgraded a system from gutsy to hardy. Before starting the do- release-upgrade -d, I removed all the kernel and modules packages that were installed under gutsy (I use my own kernel, because 2.6.24 has kernel bug 10118, and I was running out of disk space on /boot). During the "setting up" stage, I hit problems: apt refused to do anything further and told me to run dpkg --configure -a. but dpkg --configure -a failed because the initramfs-tools trigger couldn't find the appropriate /lib/modules directory. I eventually found a workaround: rm /var/lib/dpkg/triggers/initramfs-tools If initramfs-tools can't install without kernel modules installed, shouldn't it have a dependency on some modules package? Or, better still, maybe have the initramfs-tools trigger exit gracefully if it doesn't see any modules. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/220094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
