Bug 161993

Summary:	2 glibc rpms installed after upgrade from FC3 to FC4
Product:	[Fedora] Fedora	Reporter:	Hubert Verstraete <hubs>
Component:	redhat-lsb	Assignee:	Leon Ho <llch>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	4	CC:	chris.ricker
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-07-15 01:23:25 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 Hubert Verstraete 2005-06-28 22:32:12 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5

Description of problem:
After the upgrade from FC3 to FC4, I have two glibc installed:
$ rpm -q glibc
glibc-2.3.5-0.fc3.1
glibc-2.3.5-10

The first one comes from FC3. The second from FC4.
The whole content of the FC3 rpm is also contained in the FC4 rpm.

Should I and could I remove the FC3 rpm without any risk?

Version-Release number of selected component (if applicable):
glibc-2.3.5-0.fc3.1 glibc-2.3.5-10

How reproducible:
Didn't try

Steps to Reproduce:
1. fresh install Fedora Core 3
2. apply all available updates (with yum or other)
3. upgrade to Fedore Core 4

Actual Results:  Everything runs well, but it looks like I have two glibc rpms installed at once:
$ rpm -q glibc
glibc-2.3.5-0.fc3.1
glibc-2.3.5-10

Expected Results:  I would have expected:
$ rpm -q glibc
glibc-2.3.5-10

Additional info:

Comment 1 Jakub Jelinek 2005-06-29 13:34:52 UTC

That sounds like glibc's %post failed, can you find some error messages in
update.log that would show what's going on?

Comment 2 Hubert Verstraete 2005-06-29 13:42:37 UTC

You're alright, here is the error message from upgrade.log:

Upgrading glibc-2.3.5-10.i686.
error: %trigger(redhat-lsb-1.3-4.i386) scriptlet failed, exit status 255

Comment 3 Jakub Jelinek 2005-06-29 13:44:24 UTC

That suggests a bug in redhat-lsb...

Comment 4 Leon Ho 2005-07-05 01:49:12 UTC

*** Bug 160155 has been marked as a duplicate of this bug. ***

Comment 5 Chris Ricker 2005-07-05 16:36:23 UTC

This is basically a duplicate of Bug 160585 which has jbj's explanation of What
Went Wrong

Comment 6 Leon Ho 2005-07-15 01:23:25 UTC


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