Bug 210169 - Installation of RedHat Enterprise Linux 5 Client ( weekly build 10/03) errors out
Installation of RedHat Enterprise Linux 5 Client ( weekly build 10/03) errors...
Status: CLOSED DUPLICATE of bug 192709
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libgtk-java (Show other bugs)
All Linux
medium Severity urgent
: ---
: ---
Assigned To: Stepan Kasal
Depends On:
  Show dependency treegraph
Reported: 2006-10-10 11:41 EDT by Rezwanul Kabir
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-10 12:25:30 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 Rezwanul Kabir 2006-10-10 11:41:09 EDT
Description of problem:

 Installation of RHEL5 Client with customized package selection fails after 
inserting CD6. This may occur with default installation as well but haven't 
tried that. 

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

Weekly build of 10/03

How reproducible:

Steps to Reproduce:

1.Install RHEL5 Client through CDs.
2. Select REGKEY "DW"
3. Select all packages in "Development Group"
4. Proceed until the installer asks for CD 6
5. Install errors out
Actual results:

Error messages on VC6:

  "Error Running Transaction
  There was an error running your transaction for the follwoing reason: file 

Error messages on VC3:

  file error: file /usr/share/java/gtk2.8-2.8.6jar from install of libgtk-java-
2.8.6-3fc6 conflicts with file from package libgtk-java-2.8.6-3.fc6
      Error: error running transaction file /usr/share/java/gtk2.8-2.8.6.jar 
from install of libgtk-java-2.8.6-3.fc6 conflicts with file from package 

Expected results:

 Install should proceed without any error

Additional info:
Comment 1 Jeremy Katz 2006-10-10 12:14:10 EDT
Conflicts are package bugs.  I think this got fixed on Monday or so, though.

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