We do support arm64 UEFI systems for server and for those, there's no use case for flash-kernel to do anything. It does commonly get installed though. Though flash-kernel-installer knows not to make d-i install it on arm*/efi systems, it does tend to get installed via other mechanisms. curtin image-based installs, for example, do include flash-kernel. When f-k is there, it breaks kernel upgrades because the f-k kernel hooks bail out.
As Newell mentioned, the bypass-on-EFI code change in Debian only skip unknown devices. If a system does appear that has a kernel/initrd in encrypted MTD or similar, we just need to add a db entry for it like any other f-k supported device and this bypass path would not be taken. I guess an alternate solution would be to make tools like curtin, our factory image creation process, etc be smart enough to detect an efi system and set the FLASH_KERNEL_SKIP variable - but I don't see why that's any better than fixing it in one place. Unless there's any further objections, I'd like to go ahead and merge/upload w/ Newell's patch from Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517582 Title: flash-kernel causes postinsts to fail when it happens to be installed on an unsupported system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1517582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
