[FFe] [17.10 FEAT] upgrade to newest version of glibc >=2.26
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Undecided
|
Unassigned | ||
glibc (Ubuntu) |
Fix Released
|
Undecided
|
Adam Conrad |
Bug Description
[ Proposal ]
I'd like to upload glibc 2.26 today (September 5th) and aim to have all the autopkgtest regressions dealt with and the package migrated to the release pocket within a week.
[ Justification ]
Ubuntu's glibc is now two upstream revisions behind, and 2.25 and 2.26 brought in a large number of fixes and arch-specific optimizations. We want both.
[ Regression Potential ]
The upstream test suite passes on all of our architectures, and there are not too many changes noted in the upstream changelog that look like they'd cause disruption. A few obsolete headers have been removed and the like, so keeping an eye on future FTBFSes to potentially deal with that will be needed, but nothing looks hugely impactful.
[ Original Report ]
Request to upgrade to newest level of glibc 2.26. which introduced some new features for new machine...
Currently this version is under development
https:/
But should be availablle for the 17.10 Release
CVE References
tags: | added: architecture-s39064 bugnameltc-156510 severity-high targetmilestone-inin1710 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → glibc (Ubuntu) |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in glibc (Ubuntu): | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Adam Conrad (adconrad) |
status: | New → Triaged |
Changed in ubuntu-z-systems: | |
assignee: | Dimitri John Ledkov (xnox) → nobody |
status: | New → Triaged |
information type: | Private → Public |
summary: |
- [FFe] 17.10 FEAT] upgrade to newest version of glibc >=2.26 + [FFe] [17.10 FEAT] upgrade to newest version of glibc >=2.26 |
Changed in ubuntu-z-systems: | |
status: | Triaged → Fix Released |
We cannot commit to upgradeing to 2.26 before it is released publically. At that point toolchain maintainers will evaluate if we can take new glibc in, or not. Usually we do, but it may slip depending on the end timings.