mstdn.io is one of the many independent Mastodon servers you can use to participate in the fediverse.

Administered by:

Server stats:

363
active users

I was disappointed to find that my box is still on glibc 2.33, while 35 and 21.10 have been shipping 2.34 for several months.

GCC is also still at 11.1, when 11.2 has been around since last September.

Apparently, there's an issue with Arch toolchain maintainers frequently burning out when users point fingers at them of breaking their favorite application or their configuration:
bbs.archlinux.org/viewtopic.ph
(scroll down past the dismissive comments by jasonwryan)

bbs.archlinux.orgWhat is happening with glibc and gcc packages? / Arch Discussion / Arch Linux Forums

I wasn't there to see how the Arch community treated the toolchain devs, but I wonder: why couldn't toolchain updates bake for a while in testing before rolling out to everyone?

And also is Arch building glibc in some non-standard way that's exposing bugs that don't get caught by Fedora and Ubuntu?

I'm trying to understand if toolchain maintenance is inherently more complex in Arch for some reason, or there are simply fewer hands on deck to do it.