Bug 210169 - Installation of RedHat Enterprise Linux 5 Client ( weekly build 10/03) errors out
Summary: Installation of RedHat Enterprise Linux 5 Client ( weekly build 10/03) errors...
Keywords:
Status: CLOSED DUPLICATE of bug 192709
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libgtk-java
Version: 5.0
Hardware: All
OS: Linux
medium
urgent
Target Milestone: ---
: ---
Assignee: Stepan Kasal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-10 15:41 UTC by Rezwanul Kabir
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-10 16:25:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rezwanul Kabir 2006-10-10 15:41:09 UTC
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:
Always

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 
conflicts"

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 
libgtk-java-2.8.6-3.fc6


Expected results:

 Install should proceed without any error

Additional info:

Comment 1 Jeremy Katz 2006-10-10 16:14:10 UTC
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.