Bug 10825
Summary: | Upgrading 6.2 to 6.2 installs 112 MB | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Battista <cjbat> |
Component: | installer | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
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: | 2000-04-17 15:35:37 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
John Battista
2000-04-14 19:36:34 UTC
This is the default behavior; an upgrade always upgrades the 'Base' packages to the current package set to guarantee a workable environment. Perhaps this could be changed so that it doesn't upgrade the exact same version on top of itself.... This is the intended bahavior so that a user can recover from a trashed system. If we did not reinstall the base packages when the same version is already on the system, then there would be no way to recover from corrupted version of those files. The intent is that once the user has prestine versions of the base packages, then they can invoke RPM with the --force option to reinstall any other corrupted packages. |