Bug 88771 - rpm -Fhv glibc-2.3.2-27.9.i386.rpm results in broken system
rpm -Fhv glibc-2.3.2-27.9.i386.rpm results in broken system
Status: CLOSED DUPLICATE of bug 88456
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-04-13 17:07 EDT by Zenon Panoussis
Modified: 2016-11-24 10:05 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zenon Panoussis 2003-04-13 17:07:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Upgrading from glibc-2.3.2-11.9 to glibc-2.3.2-27.9.i386 leaves *both* versions
on the system. Once that happens, everything segfaults. On reboot (brutal
reboot, the reboot command segfaults too), init gets confused, spits out a
"respawning too fast, disabled for 5 minutes" message for each and every
runlevel and stalls. 

Workaround: Boot from another installation/CD. If 
   # rpm -qa --root /your/root |grep glibc 
shows both versions of glibc present, do
   # rpm --force --root /your/root -e glibc-2.3.2-11.9 
and reboot again.

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

How reproducible:

Steps to Reproduce:
This happened to me on two different systems. 

Expected Results:  The later version should uninstall the earlier one.
Comment 1 Jakub Jelinek 2003-04-13 17:10:47 EDT
Why are you "upgrading" from i686 version to i386 one?

*** This bug has been marked as a duplicate of 88456 ***
Comment 2 Zenon Panoussis 2003-04-13 17:44:28 EDT
Perhaps because I was too charmed by "wget -nd *; rpm -Fhv *.rpm". This still
shouldn't happen. 

BTW, having read the discussion on 88456, I can add that was upgrading 9, not
from 8.0. 
Comment 3 Red Hat Bugzilla 2006-02-21 13:52:39 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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