Bug 161624
Summary: | As built, gd requires glibc > 2.3.3 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeff Spirko <spirko> |
Component: | gd | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | rvokal |
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: | 2005-06-27 09:39:41 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
Jeff Spirko
2005-06-24 21:21:05 UTC
Such partial updates can often lead to such problems and it's not a gd specific problem. Unfortunately there are only 3 possible ways out of this: 1) Update gd with yum and pull in all required dependant updates as well 2) Don't update gd 3) Rebuild the FC4 srpm on the FC3 system and install that. Read ya, Phil I was doing (1). My point was that gd-2.0.33-2 isn't marked as requiring an update of glibc from 2.3.3 to 2.3.5, though it should be. After manually updating to glibc-2.3.5-10, gd now works fine. |