Bug 24735
Summary: | packages not upgraded during 6.2->7.0 upgrade | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | josip |
Component: | gnorpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | nicku |
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-23 22:32:43 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
josip
2001-01-23 20:11:37 UTC
I forgot to say that the 7.0 bugfix gnorpm-0.95.1-5.i386.rpm does NOT replace the 6.2 bugfix gnorpm-0.95.1-5.6x.i386.rpm when using the usual 'rpm -U gnorpm-0.95.1-5.i386.rpm'. One has to use the --force flag as well. Over a dozen other packages fail their 'rpm -Vp [redhat-package-file]' md5 file tests after upgrade (6.2+bugfixes)->7.0->(7.0+bugfixes), indicating that this problem is more general than just gnorpm. |