Red Hat Bugzilla – Bug 88771
rpm -Fhv glibc-2.3.2-27.9.i386.rpm results in broken system
Last modified: 2016-11-24 10:05:52 EST
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): glibc-2.3.2-27.9 How reproducible: Twice Steps to Reproduce: This happened to me on two different systems. Expected Results: The later version should uninstall the earlier one.
Why are you "upgrading" from i686 version to i386 one? *** This bug has been marked as a duplicate of 88456 ***
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.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.