Bug 2968 - Upgrade from 5.2 will cause lots of missing files
Upgrade from 5.2 will cause lots of missing files
Status: CLOSED DUPLICATE of bug 2727
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-05-22 11:42 EDT by david.kastrup
Modified: 2015-01-07 18:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-05-22 13:49:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description david.kastrup 1999-05-22 11:42:16 EDT
After upgrading two entirely different systems from 5.2 to
6.0, I noticed that quite a few packages would not work
properly due to missing files.  Please do an
rpm --verify -a
after attempting such an upgrade.  You will find hosts of
missing files.  I have the suspicion that there is a
correlation between packages that install .rpmorig files and
this phenomenon, but at least with the tetex-latex package,
which is missing wagonloads of files after the upgrade, no
.rpmorig file was noted in the upgrade log.

This upgrade bug seems to me to be the source for bug report
2080, too.

Affected packages can be reinstalled with
rpm -U --force

About a dozen different and unrelated packages are
affected.  Since this affects every upgrade from 5.2 to 6.0,
the severity is rather high as it causes hundreds of
thousands inconsistent RedHat 6.0 systems.  Please add
upgrades to your release testing.  As verifying an upgraded
system is a single call of rpm, this is cheap to do.

I have flagged this as an i386 error since that is the
system I use.  Thius does not mean that other architectures
might not also be affected.
Comment 1 Bill Nottingham 1999-05-22 13:49:59 EDT
*** This bug has been marked as a duplicate of 2727 ***

Note You need to log in before you can comment on or make changes to this bug.