The GNU C Library version 2.25
Switch glibc in Fedora 26 to glibc version 2.25.
- Name: Carlos O'Donell
- Email: firstname.lastname@example.org
- Release notes owner:
The GNU C Library version 2.25 will be released at the beginning of February 2017; we have started closely tracking the glibc 2.25 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 26 will branch after the GLIBC 2.25 upstream release.
Benefit to Fedora
Stays up to date with latests security and bug fixes from glibc.
The packaging changes will provide a small reduction in disk space needed by minimal installations.
- Proposal owners: Update glibc to 2.25 from tested upstream release.
- Other developers: Aside from Carlos O'Donell <email@example.com>, DJ Delorie <firstname.lastname@example.org>, Florian Weimer <email@example.com>, Torvald Riegel <firstname.lastname@example.org>, Martin Sebor <email@example.com>, and Patsy Franklin <firstname.lastname@example.org>, no other developers are required. These developers need to ensure that rawhide is stable and ready for the Fedora 26 branch. Given that glibc is backwards compatible and we have been testing the new glibc in rawhide it should make very little impact when updated.
- Release engineering: All Fedora releases must be released using a released version of glibc. The Fedora glibc team is responsible for ensuring that Fedora Rawhide stabilizes 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 glibc or other components, the Fedora glibc team will ensure coordination with release engineering such that a mass rebuild uses the released version of glibc to fix any last minute ABI changes. The GNU C Library (glibc) does not require a mass rebuild for this release.
- Policies and guidelines: The policies and guidelines do not need to be updated.
The library is backwards compatible with the version of glibc that was shipped in Fedora 25.
Some packaging changes required, see: https://sourceware.org/glibc/wiki/Release/2.25#Packaging_Changes
We fully expect to fix all packaging changes in Fedora Rawhide given that glibc in Rawhide is tracking what will become glibc 2.25.
How To Test
The GNU C Library has its own testsuite, which is run during the package build and examined by the glibc developers before being uploaded. This test suite has 1000+ tests that run to verify the correct operation of the library. In the future we'll also be running the microbenchmark to look for performance regressions as well as behavioural ones.
Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc. The glibc 2.25 NEWS update will include more details.
All packages do not need to be rebuilt, but applications will benefit from the mass rebuild, so that they pick up the new
- Contingency mechanism: Given that Rawhide has started tracking GLIBC 2.25, no show-stopper problems are expected. At this point, we can still revert to upstream version 2.24 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.
- Contingency deadline: Alpha freeze.
- Blocks release? Upgrading glibc does block the release. We should not ship without a newer glibc, there will be gcc and language features that depend on glibc being upgraded. Thus without the upgrade some features will be disabled or fall back to less optimal implementations.
The glibc manual contains the documentation for the release and doesn't need any more additional work.
The GNU C Library version 2.25 will be released at the beginning of Feburary 2017. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD