It seems to me that the mere installation of an installable package - even if it isn't useful on the platform - shouldn't start breaking kernel upgrades. And users shouldn't be expected to know that there's a magic envvar they have to set to to avoid it.
The question is - does it ever make sense to run flash-kernel on an EFI system? We've been working around this for non-EFI systems that should not run f-k by adding no-op entries in the f-k db (e.g. VMs). Systems in EFI mode seem like a whole class of systems we can blacklist all at once. -- 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
