codonell reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
All Fedora releases must be released using a released and supported version of the core
toolchain involving glibc, gcc, and binutils.
The Fedora toolchain team is responsible for ensuring that Fedora Rawhide stabilizes
static linking, code generation, and library ABI, before a Fedora release, or that after
the branch that the Fedora release is rebased (a very small rebase) to the final released
version. This is a requirement for Fedora to inherit the ABI and API guarantees provided
by upstream. If a mass rebuild is required by binutils, gcc, glibc or other components,
the Fedora toolcahin team will ensure coordination with release engineering such that a
mass rebuild uses the released version of all components and fix any last minute ABI or
code-generation changes.
* When do you need this? (2019/01/30)
We need a mass rebuild.
Change page for review:
https://fedoraproject.org/wiki/Changes/GLIBC229
Owner: Carlos O'Donell carlos(a)redhat.com
glibc mass rebuild request: This request.
Change page for review:
https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition
Owner: Carlos O'Donell carlos(a)redhat.com
glibc mass rebuild request: ppc64le transition to 128-bit IEEE long double.
GCC will file a system-wide change request for GCC 9 transition also in December.
Binutils will remain as 2.31.1 and will not change (Nick Clifton's notes).
* If we cannot complete your request, what is the impact?
I we cannot do a mass rebuild then we should not transition to glibc 2.29 or gcc 9, but we
might still be able to transition via targeted mass rebuilds.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7907