Bug 793692 (glibc-2.33-stable) – sys-libs/glibc-2.33 sys-libs/glibc-2.32-r8 stabilization

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Andreas K. Hüttel 2021-06-01 09:55:39 UTC]

Arches please TEST and then stabilize. 

glibc-2.32-r8:
* patchset upgrade 6 => 8
* various minor upstream release branch fixes
  (elf parsing, x86_64, arm64)
* fix for CVE-2021-3326 (JP locale)
* enable nss-systemd in nsswitch.conf by default

glibc-2.33:
* version upgrade, see 
  https://sourceware.org/pipermail/libc-alpha/2021-February/122207.html
* fix for CVE-2021-3326 (JP locale) (included upstream)
* enable nss-systemd in nsswitch.conf by default

Bug 769989 is the only remaining issue related to 2.33 in Gentoo bugzilla. The RedHat patch works [1] , Google is not telling why it reverted it in Chromium upstream [2], and there has been no motion at all since Fri, Apr 16, 2021. Accordingly we go ahead.
(Note that bug 769989 only affects Chromium *built* on 2.33, not Chromium built on older glibc and running on 2.33.)

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1164975#c22
[2] https://chromium.googlesource.com/chromium/src/+/8079cee5f9f963f525051a53128affdcf9dc3fa4

[Comment 1 Sam James 2021-06-01 13:55:52 UTC]

arm done

[Comment 2 Sam James 2021-06-01 13:57:33 UTC]

sparc done

[Comment 3 Sam James 2021-06-01 17:58:01 UTC]

x86 done

[Comment 4 Sam James 2021-06-01 17:58:03 UTC]

ppc done

[Comment 5 Sam James 2021-06-01 17:58:05 UTC]

ppc64 done

[Comment 6 Sam James 2021-06-01 19:58:14 UTC]

amd64 done

[Comment 7 Sam James 2021-06-02 10:38:01 UTC]

arm64 done

[Comment 8 Rolf Eike Beer 2021-06-13 11:20:14 UTC]

hppa done, bug done