Bug 3603 - slight packaging error
slight packaging error
Status: CLOSED WORKSFORME
Product: Red Hat Raw Hide
Classification: Retired
Component: tetex (Show other bugs)
1.0
i386 Linux
low Severity low
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-20 17:36 EDT by Jay Freeman
Modified: 2017-03-08 20:44 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-12 18:37:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jay Freeman 1999-06-20 17:36:31 EDT
While installing the new 1.0.1-2 tetex packages I got the
following:

[root(2)@ironclad RPMs]# rpm -Uhv tetex*-1.0.1-2.i386.rpm
....
package README not found in file index
<previous line another 12 times or so>
tetex-dvilj
##################################################
....
Comment 1 Jay Freeman 1999-06-20 22:34:59 EDT
After installing more of the new packages, I am getting that more and
more often, and it seems to be on the uninstallation of the old
package, not the installation of the new one, so I am assuming that
this is a new requirement that the new version of RPM is forcing,
hence the new RPMs. Nevermind :)
Comment 2 Cristian Gafton 1999-06-24 14:40:59 EDT
rpm --rebuilddb should take care of this?
Comment 3 Jeff Johnson 1999-08-12 18:37:59 EDT
I've seen this problem and believe that it is caused by not having
done "rpm --rebuilddb" when upgrading rpm. Please reopen this bug
if that is not the case.
Comment 4 openshift-github-bot 2017-03-08 20:44:26 EST
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/29886dbe6054aa46f948b0e38394726343abc2a2
Merge pull request #3604 from sdodson/issue3603

openshift_excluders depends on openshift_repos

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