Bug 30006

Summary:	update request glibs2.0 before release version 2.35
Product:	Mageia	Reporter:	Nikolay Sabelnikov <79625490833>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	79625490833, fri, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://sourceware.org/pipermail/libc-alpha/2022-February/136040.html
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Nikolay Sabelnikov 2022-02-06 08:16:23 CET

Officially released to version 2.35, and you have cauldron only version 2.32

Nikolay Sabelnikov 2022-02-06 08:16:41 CET

CC: (none) => 79625490833

Comment 1 sturmvogel 2022-02-06 08:34:53 CET

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

Comment 2 Nikolay Sabelnikov 2022-02-06 08:47:33 CET

Ok, I will use this service in the future.

Comment 3 Morgan Leijström 2022-02-06 12:04:58 CET

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

Comment 4 Morgan Leijström 2022-02-06 13:02:13 CET

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.

Comment 5 Lewis Smith 2022-02-06 21:56:02 CET

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 => RESOLVED
CC: (none) => tmb
Resolution: (none) => INVALID

Comment 6 Thomas Backlund 2022-02-06 22:01:07 CET

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 ...