Bug 746864

Summary:	yum-builddep qt-x11 installs a version of libc incompatible with yum
Product:	[Fedora] Fedora	Reporter:	416365416c
Component:	glibc	Assignee:	Andreas Schwab <schwab>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	ffesti, fweimer, jakub, james.antill, jwest, maxamillion, pmatilai, schwab, tla, zpavlas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-26 11:22:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description 416365416c 2011-10-18 02:56:28 UTC

Description of problem:
after 'yum-builddep qt-x11', any use of yum (or 'import yum' in a python interpeter) leads to an error.


Version-Release number of selected component (if applicable):
Fedora 16 beta


Steps to Reproduce:
1. yum-builddep qt-x11
2. yum --version
  
Actual output:
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

/lib64/libglib-2.0.so.0: symbol __fdelt_chk, version GLIBC_2.15 not defined in file libc.so.6 with link time reference

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.2 (default, Jul  8 2011, 18:54:13)
[GCC 4.6.1 20110627 (Red Hat 4.6.1-1)]

Expected output:
Version information of yum is output

Comment 1 416365416c 2011-10-18 04:36:22 UTC

This was on a fresh install of the F16 Beta before a 'yum update', so the problem may have been that the updated glibc got pulled without the updated yum that works with it. After a 'yum update', 'yum-builddep qt-x11' doesn't break yum.

Arguably still a bug, as it is not easy to update to the latest yum once the broken state is reached.

Comment 2 Jeremy West 2011-10-24 19:13:34 UTC

I encountered this after doing a base install using the XFCE media, then doing a $ yum groupinstall 'GNOME Desktop Environment'

Now I can no longer use yum.  Awesome.

Comment 3 James Antill 2011-10-24 20:08:07 UTC

There have been a couple of glibc problems in F16, I assume this is fixed now given comment #1.

Comment 4 Andreas Schwab 2011-10-26 11:22:22 UTC


*** This bug has been marked as a duplicate of bug 743923 ***