Comment 3 for bug 348660

Looking at this in a bit more depth, I think flash-kernel-installer needs rework to not expect to do everything in the postinst, and a ubiquity component written to drive flash-kernel-installer, and flash-kernel added to ubiquity as bootloader-depends in debian/rules. Additionally, flash-kernel-installer probably needs to be reviewed to ensure it sets appropriate sucess/failure in a way that ubiquity can report effectively, and that this doesn't break use in a pure d-i environment.

In the short term, as long as users aren't expecting a bootloader to be installed, the quick hack described lp:~persia/ubiquity/no-bootloader-installer-for-armel should avoid the ubiquity error until the rest can be resolved. A better quick hack would present a non-fatal warning to the user (which requires templates definition, etc.).