Officially released to version 2.35, and you have cauldron only version 2.32
CC: (none) => 79625490833
Please use our Mageia application database to look for precise names and versions: https://madb.mageia.org/ In cauldron: glibc-2.34-26.mga9.x86_64.rpm In Mga 8: glibc-2.32-23.mga8.x86_64.rpm In Mga8 updates testing: glibc-2.32-25.mga8.x86_64.rpm
Ok, I will use this service in the future.
Please update the fields :) Overall, this may better be submitted in the form of first posting a question on dev list. Because so much depends on it, maybe constraints of what need be done before/after need be aired. Seeing Cauldron already have iteration -26 of version 2.34, I guess packager is tracking it well already.
CC: (none) => fri
You can also search for both open and recently closed bugs on the package. For example the open bug 29935 on patching security issues in glibc.
It is unclear which SRPM this bug refers to. 'glibs2.0' does not exist. We have 'glibc' (2.34) of course, and 'glib2.0' (2.70.3). > Officially released to version 2.35, and you have cauldron only version 2.32 You can be sure that we keep up to date with glibc up to a point, but not necessarily to the latest 'official release'. It is certainly a package that does not require users asking us to update it! - unless for a very good reason. CC'ing tmb for info, bug closed.
Source RPM: Glibs2.0 => (none)Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => INVALID
Yeah, I will push new glibc when I consider it ready, not just because it's released upstream... just as a fun datapoint of why I prefer to wait a bit when it comes to low level bits like glibc... within 12 hours of 2.35 release, there was already 4 follow-up fixes added ...