gcc-10 backport to bionic needed for grub2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Triaged
|
High
|
Unassigned |
Bug Description
grub2-unsigned is now being binary-copied from kinetic back to all stable series, in order to avoid re-signing the UEFI binaries multiple times for the same code changes.
Current grub2-unsigned build-depends on gcc-10. This package does not exist in bionic - but because the binaries were copied from a later series, this was not a build failure that blocked the grub2-unsigned binaries being published in bionic.
Nevertheless, we require that all packages be rebuildable from source using build-dependencies *within* the given series. So this is a bug that needs to be addressed.
There are two options: either we publish a separate source version of grub2-unsigned for bionic that rolls back the build-dependency on gcc-10; or, we publish gcc-10 to bionic as a non-default compiler that doesn't take over any of the binary packages from gcc-9 in that series (notably: libgcc).
tags: | added: foundations-todo |
I recall there being some reason why we cared about building grub with a newer toolchain, either because the newer toolchain is needed to have not-buggy output or because it is needed for grub to not drop features. But I don't know the details, so I've added Julian to the bug to provide that information.