This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 161993 - 2 glibc rpms installed after upgrade from FC3 to FC4
2 glibc rpms installed after upgrade from FC3 to FC4
Status: CLOSED DUPLICATE of bug 160585
Product: Fedora
Classification: Fedora
Component: redhat-lsb (Show other bugs)
4
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Leon Ho
:
: 160155 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-28 18:32 EDT by Hubert Verstraete
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-14 21:23:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Hubert Verstraete 2005-06-28 18:32:12 EDT
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 09:34:52 EDT
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 09:42:37 EDT
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 09:44:24 EDT
That suggests a bug in redhat-lsb...
Comment 4 Leon Ho 2005-07-04 21:49:12 EDT
*** Bug 160155 has been marked as a duplicate of this bug. ***
Comment 5 Chris Ricker 2005-07-05 12:36:23 EDT
This is basically a duplicate of Bug 160585 which has jbj's explanation of What
Went Wrong
Comment 6 Leon Ho 2005-07-14 21:23:25 EDT

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

Note You need to log in before you can comment on or make changes to this bug.