Bug 24347
Summary: | !glibc-2.2-12.i386.rpm unable to Upgrade! | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <ml> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | fweimer |
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: | 2001-01-19 10:22:34 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
Need Real Name
2001-01-19 10:21:06 UTC
If you read e.g. the errata page for glibc, it mentions you have to rpm -Uvh glibc-2.2-12.i386.rpm glibc-common-2.2-12.i386.rpm and then do the usual -Fvh stuff. That's because glibc was split into two subpackages and the intent is to require both to be installed at once. The reason why it was split is to save space: glibc-common is only i386 while glibc is i386 and i686 (similarly for other arches). |