Bug 702836

Summary:	GLIBC Compiler Version Issue
Product:	[Fedora] Fedora	Reporter:	Wayne Borean <wborean>
Component:	glibc	Assignee:	Andreas Schwab <schwab>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	15	CC:	fweimer, jakub, schwab
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-08 22:28:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Wayne Borean 2011-05-07 15:42:37 UTC

Description of problem: Fresh install of Fedora 15 Beta on new hardware. Found a lot of software would not install. Common error message was:

glibc-utils-2.13.90-9.i686 requires glibc = 2.13.90-9
glibc-devel-2.13.90-9.i686 requires glibc = 2.13.90-9
glibc-headers-2.13.90-9.i686 requires glibc = 2.13.90-9

When I checked I found out that the compiler version installed is  2.13.90-10

Version-Release number of selected component (if applicable):2.13.90-10


How reproducible:100%


Steps to Reproduce:
1. Try to install any programming tool using gpk-application.
2. Try to install any other Desktop (i.e. KDE) using gpk-application.
3. Try to install anything that comes as source using gpk-application.
  
Actual results: The install will fail giving one of the following messages:

glibc-utils-2.13.90-9.i686 requires glibc = 2.13.90-9
glibc-devel-2.13.90-9.i686 requires glibc = 2.13.90-9
glibc-headers-2.13.90-9.i686 requires glibc = 2.13.90-9

or 

glibc-devel-2.13.90-9.i686 requires glibc = 2.13.90-9
glibc-headers-2.13.90-9.i686 requires glibc = 2.13.90-9

Expected results: Normally the application installs. 


Additional info: Never seen this before, but then again, this is the first time I've run a Fedora Beta.

Wayne

Comment 1 Wayne Borean 2011-05-08 22:28:10 UTC

Problem is now gone - appears to have been related to an update to the compiler package that wasn't completed.