Bug 1019833 - YUM errors out Running rpm_check_debug
YUM errors out Running rpm_check_debug
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum (Show other bugs)
5.9
x86_64 Linux
unspecified Severity high
: rc
: ---
Assigned To: packaging-team-maint
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-16 09:20 EDT by wtrzop
Modified: 2013-10-16 11:20 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-16 11:20:10 EDT
Type: Bug
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 wtrzop 2013-10-16 09:20:07 EDT
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 11:20:10 EDT
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.