Summary: | sys-libs/glibc-2.17: stabilize | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | alexander, axiator, josef64, nikoli |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 448860 | ||
Bug Blocks: |
Description
SpanKY
2014-01-02 11:25:49 UTC
alpha stable Just out of curiosity, since glibc 2.16 just went stable 2 months ago, why 2.17 so soon? (In reply to Steev Klimaszewski from comment #2) because 2.16 should have gone stable way sooner than it did amd64 stable x86 stable Now that it is stable sys-libs/glibc-2.17 why not add some security patches I found from Debian: https://bugs.gentoo.org/show_bug.cgi?id=494444 runs well with my Gentoo~unstable~amd64 not hardened Please look at my patch in details mode to understand what is CVE and one patch is not, but I think is important. ppc stable ppc64 stable arm stable ia64 marked stable sparc stable. Closing. |