Bug 671160 - yum won't run
yum won't run
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum (Show other bugs)
5.5
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: James Antill
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-20 11:15 EST by Jeff
Modified: 2014-01-21 01:20 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-20 11:38:17 EST
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 Jeff 2011-01-20 11:15:15 EST
Description of problem:
ERROR with rpm_check_debug vs depsolve:
freetype is needed by (installed) freetype-utils-2.1.9-17.el4_8.1.i386

Version-Release number of selected component (if applicable):
Linux farkel.res.redprairie.com 2.6.18-186.el5 #1 SMP Wed Jan 27 18:14:15 EST 2010 i686 i686 i386 GNU/Linux
Red Hat Enterprise Linux Server release 5.5 Beta (Tikanga)
You have new mail in /var/spool/mail/root

How reproducible:
Every attempt to run YUM fails.
This system was upgraded from RH4 to RH5.5

Steps to Reproduce:
1. yum update
2.
3.
  
Actual results:
ERROR with rpm_check_debug vs depsolve:
freetype is needed by (installed) freetype-utils-2.1.9-17.el4_8.1.i386

Expected results:
update/upgrade work

Additional info:
Comment 1 James Antill 2011-01-20 11:38:17 EST
> This system was upgraded from RH4 to RH5.5

This isn't supported, AFAIK. You should probably talk with your support contact.

> freetype is needed by (installed) freetype-utils-2.1.9-17.el4_8.1.i386

My most obvious guess is that the rpmdb is currently "broken" in some way. You can try:

rpm -Va --nofiles --nodigest
yum list '*el4*'
package-cleanup --problems
package-cleanup --dupes

...but again, you might want to phone someone up.

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