[Bug 2015801] Re: gcc-10 backport to bionic needed for grub2

Julian Andres Klode 2015801 at bugs.launchpad.net
Tue Apr 11 12:51:41 UTC 2023


You also cannot necessarily produce working binaries without the correct
versions of binutils. Stuff fails with sections not being aligned and
issues like that. Everything messy.

I do not think we are super interested in gcc-10 backporting right now,
grub needs to move to gcc-12 soon anyhow, Debian already moved.

Starting with the opening of lunar+1, stable fwupd-efi, grub, shim
releases will be built from lunar.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2015801

Title:
  gcc-10 backport to bionic needed for grub2

Status in gcc-10 package in Ubuntu:
  Invalid
Status in gcc-10 source package in Bionic:
  Triaged

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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2015801/+subscriptions




More information about the foundations-bugs mailing list