Bug 32379 - Cannot update glibc due to problems with dependencies
Summary: Cannot update glibc due to problems with dependencies
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-12 12:41 CEST by Frédéric "LpSolit" Buclin
Modified: 2023-10-12 20:39 CEST (History)
1 user (show)

See Also:
Source RPM: glibc-2.32-32.mga8
CVE:
Status comment:

Attachments
screenshot (118.74 KB, image/png)
2023-10-12 12:41 CEST, Frédéric "LpSolit" Buclin 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Frédéric "LpSolit" Buclin 2023-10-12 12:41:41 CEST 
Created attachment 14049 [details]
screenshot

The update to glibc-2.32-32.mga8 fails due to dependencies errors, see the screenshot.
Thomas Andrews 2023-10-12 17:31:50 CEST

Depends on: 32357 => (none)

Comment 1 katnatek 2023-10-12 18:26:07 CEST 
(In reply to Frédéric "LpSolit" Buclin from comment #0)
> Created attachment 14049 [details]
> screenshot
> 
> The update to glibc-2.32-32.mga8 fails due to dependencies errors, see the
> screenshot.

Is asking you to install glibc-devel
Comment 2 Lewis Smith 2023-10-12 20:26:21 CEST 
I thought glibc-devel is always installed. The error is citing >=2.4-1 ; could it be that the pkg is installed but not recent enough?
I must have a look at M8.

@Frédéric
You must have updated glibc often enough. Is this a problem just with the most recent update?

CC: (none) => lewyssmith

Comment 3 Frédéric "LpSolit" Buclin 2023-10-12 20:39:25 CEST 
(In reply to Lewis Smith from comment #2)
> I thought glibc-devel is always installed. The error is citing >=2.4-1 ;
> could it be that the pkg is installed but not recent enough?

Yes, that's the reason of the problem. I forgot I added /^glibc/ to /etc/urpmi/skip.list some time ago because glibc was in Testing and it prevented other packages from being listed. Removing it from skip.list fixes the problem.

Sorry for the noise.

Resolution: (none) => INVALID
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.