Bug 174592 - xchat-gnome fails to install on latest rawhide
Summary: xchat-gnome fails to install on latest rawhide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat-gnome
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-30 15:21 UTC by Josh Boyer
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-30 18:11:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Boyer 2005-11-30 15:21:04 UTC
Description of problem:

Installing xchat-gnome on the latest rawhide results in a transaction error
because of a conflict with the xchat package.

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

xchat-gnome-0.7-2.fc5

How reproducible:

Always

Steps to Reproduce:
1. Update to latest rawhide
2. yum install xchat-gnome
3.
  
Actual results:

Transaction Check Error:  file /usr/bin/xchat-remote from install of
xchat-gnome-0.7-2.fc5 conflicts with file from package xchat-2.6.0-2

Expected results:

xchat-gnome installs

Additional info:

Comment 1 Brian Pepple 2005-11-30 16:50:14 UTC
Until I get a patch to fix this, I'll disable dbus support in devel.  Upstream
is starting to maintain their own tree, instead of just dropping in the
xchat-gnome fe into the xchat cvs, so once I write a patch, I can send it off to
Trowbridge for upstream.

Comment 2 Brian Pepple 2005-11-30 21:41:17 UTC
My patch for this has been applied upstream, and once I get some free time I'll
backport it to 0.7.

http://bugzilla.gnome.org/show_bug.cgi?id=322871

Comment 3 Josh Boyer 2005-11-30 21:46:40 UTC
Awesome.  Thanks for the quick response

Comment 4 Brian Pepple 2005-12-30 18:11:34 UTC
This is resolved with the new version that should be available once it's been
signed.


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