Bug 88097
| Summary: | rpm becomes useless when removing glibc | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <lethalwp> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-04-17 14:33:59 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: | |||
You should NEVER remove glibc. If you want to install the same version of glibc
of a specific arch:
rpm -Uvh glibc*.i686.rpm --force
You can query the arch of the installed package like this.
rpm -q --qf %{ARCH} glibc
Lots of people want statically linked rpm, but that should be its own
discussion. File a separate RFE and/or talk on shrike-list or rpm-list.
I recommend this CLOSED NOTABUG.
/usr/lib/rpm/rpmi is statically linked like /bin/rpm used to be. (/bin/rpm can no longer be statically linked for other reasons.) |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: when removing glibc (yes this happened to me because i wanted to be sure i had the i686 version and not the i386), rpm being not statically linked is rendered useless, which means you get in trouble in reinstalling the wanted package Version-Release number of selected component (if applicable): rpm-4.2-0.69 How reproducible: Always Steps to Reproduce: 1. rpm -e glibc --nodeps 2. rpm -Uvh glibc-....-i686.rpm 3. Actual Results: can't load library .....so Expected Results: installing newer glibc Additional info: "easy but nasty" workaround: from another computer, extract the library files required and the sash shell, then (you need to have an already mounted nfs share), run shash, copy the files to /lib, and reinstall the needed glibc