Bug 1019833 - YUM errors out Running rpm_check_debug
Summary: YUM errors out Running rpm_check_debug
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum
Version: 5.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 13:20 UTC by wtrzop
Modified: 2013-10-16 15:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-16 15:20:10 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description wtrzop 2013-10-16 13:20:07 UTC
Description of problem:
ERROR with rpm_check_debug vs depsolve:
libgcj-devel is needed by (installed) gcc-java-4.1.2-52.el5.x86_64
libgcj-devel is needed by (installed) gcc-java-4.1.2-52.el5.x86_64
libgcj-devel is needed by (installed) gcc-java-4.1.2-52.el5.x86_64
libgcj-devel is needed by (installed) gcc-java-4.1.2-52.el5.x86_64
Complete!
(1, [u'Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%205&component=yum'])

The reported libgcj-devel is already installed


Version-Release number of selected component (if applicable):

package gcc-java-4.1.2-54.el5.x86_64 is already installed
package libgcj-devel-4.1.2-54.el5.x86_64 is already installed


How reproducible:
 Happens every time 

Steps to Reproduce:
1. From base install - run yum update
2.
3.

Actual results:

Update fails to launch

Expected results:

Successful update with no error
Additional info:

Comment 1 Jan Zeleny 2013-10-16 15:20:10 UTC
That's not a bug in yum, that's probably some sort of suboptimal packaging or something like that. Yum just reports that libgcj-devel cannot be updated/replaced/whatever_is_needed_to_perform_the_update because gcc-java depends on it. Uninstalling gcc-java should solve the issue (probably a discontinued package?).


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