Bug 61024
Summary: | up2date fails to run | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Tim Wunder <wundertp> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | gafton, mihai.ibanescu, srevivo |
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: | 2002-05-09 13:51:23 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
Tim Wunder
2002-03-12 13:06:25 UTC
You will need to update to the latest glibc by hand. OK. Some quick questions, though: When updating glibc from RPM, is it a good idea to force the update with 'rpm -Uvh --force'? Then again, would I be better served by updating to RedHat 7.3, and starting from a more current code base? If so, is it feasible to update 7.0 to 7.3, or would a reinstall be recommended? No need to use "--force" to upgrade glibc (I would stronly recomended against useing it with rpm....) |