Summary: | sys-libs/glibc-2.31-r6 sys-libs/glibc-2.30-r9 stabilization | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Stabilization | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | axiator, sam |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | Flags: | nattka:
sanity-check-
|
Hardware: | All | ||
OS: | Linux | ||
URL: | https://sourceware.org/glibc/wiki/Release/2.31 | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=708318 | ||
Whiteboard: | |||
Package list: |
sys-libs/glibc-2.30-r9
sys-libs/glibc-2.31-r6
|
Runtime testing required: | --- |
Bug Depends on: | 709416, 717956, 720024, 727736, 727738, 727740, 727742, 727744, 727762, 732234 | ||
Bug Blocks: | 717058 |
Description
Andreas K. Hüttel
2020-06-10 06:30:41 UTC
Arches please test and stabilize: sys-libs/glibc-2.30-r9 sys-libs/glibc-2.31-r6 Notes on the two versions: sys-libs/glibc-2.30-r9 ---------------------- This version is largely identical to current stable. It contains precisely one change: an important bugfix (only) for sparc (where it already is stable). As such, even though few users will have tried this version, it should be unproblematic. There may be test failures, but please *only* have them block anything if they are regressions compared to current stable (2.30-r8). sys-libs/glibc-2.31-r6 ---------------------- True version bump. See $URL for the upstream release notes, and also https://wiki.gentoo.org/wiki/Project:Toolchain#glibc-2.31 All blockers that we know of are fixed. The test suite should pass on amd64. On other arches, your mileage may vary (please also see the upstream wiki). arm64 stable arm stable amd64 stable sparc done x86 done hppa stable ppc stable ppc64 stable Closing! \o/ s390@ was missed @ s390: ping (In reply to Andreas K. Hüttel from comment #12) > @ s390: ping s390: ping! Unable to check for sanity:
> package masked: sys-libs/glibc-2.30-r9
For s390, I stabled bug 759640 instead. dilfridge said no need to bother backdating to this bug. I can if you guys change your mind but IMO no need. |