Hi, toolchain@ would appreciate if folks could keyword glibc-2.34 locally on non-production machines to help root out any bugs.
The tracker bug is doing pretty well at this point with most remaining issues being in last-rited packages or being tracked upstream: https://bugs.gentoo.org/803482. There are no plans to keyword glibc-2.34 yet given there's a few large changes and we've not yet got over the libxcrypt hump (that's coming very shortly, stabilisation planned for 2021-11-01!). But you can't start planning too early ;) I would not recommend doing this on a machine with Chromium or anything Electron based for now as I haven't had a chance to check if the sandbox stuff has been updated. I _think_ Firefox is fine now (at least in the latest versions >= 91?). If you're able, please therefore keyword glibc-2.34 on systems where you're up for a bit of experimentation, and ideally rebuild (-ev @world) and report any bugs. If you feel generous, run FEATURES=test on some/all stuff too. Please drop into #gentoo-toolchain if you have any questions or issues we need to debug together. Cheers! Best, sam
