Bug 3372

Summary:	If glibc is available as update in Core Update Testing, all other updates are hidden
Product:	Mageia	Reporter:	Frédéric "LpSolit" Buclin <LpSolit>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins
Version:	1	Keywords:	Triaged
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	urpmi	CVE:
Status comment:

Description Frédéric "LpSolit" Buclin 2011-11-16 19:08:46 CET

When glibc is available in Core Update, I can understand why it must be installed first before anything else. But when glibc is in Core Update Testing, and if I don't want to take the risk to install it, I have no (easy?) way to ignore it and have other updates listed. Maybe all updates should be listed when still being in Testing?

If this is the desired behavior, then close this bug as wontfix.

Comment 1 Manuel Hiebel 2011-11-16 19:23:13 CET

Hi, thanks for reporting this bug.
Thierry, for you I guess ?

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => urpmi

Comment 2 Dave Hodgins 2011-11-16 19:28:07 CET

Try temporarily adding it to /etc/urpmi/skip.list

CC: (none) => davidwhodgins

Comment 3 Thierry Vignaud 2011-11-17 12:14:41 CET

I don't see any bug at all here.
If you enabled the Core Update Testing, and urpmi will (rightly) offer you to upgrade glibc (as well as other priority packages) before upgrading the rest.
You may blacklist glibc in skip.list but then you may break some package that would depend on new glibc symbols...

Status: NEW => RESOLVED
Resolution: (none) => INVALID