Bug 183449 - X-Chat 2.6.1 has been out for almost 2 months, still not in Rawhide
Summary: X-Chat 2.6.1 has been out for almost 2 months, still not in Rawhide
Keywords:
Status: CLOSED DUPLICATE of bug 201116
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
URL: http://www.xchat.org
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-01 04:53 UTC by Kevin Kofler
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-05 23:35:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xchat-2.6.6-simplify-to-use-gnome-open-for-default-webbrowser.patch (391 bytes, patch)
2006-07-28 17:23 UTC, Remi Collet
no flags Details | Diff
Updated spec file (19.52 KB, application/octet-stream)
2006-07-29 07:23 UTC, Remi Collet
no flags Details

Description Kevin Kofler 2006-03-01 04:53:04 UTC
X-Chat in Rawhide is out of date (2.6.0, 2.6.1 released on January 6th). Any 
chance we'll see it upgraded before FC5 (or at FC5 release)?

Comment 1 Christopher Aillon 2006-03-01 16:17:36 UTC
Are you collecting version numbers or is there a specific feature you'd like to see?

Comment 2 Kevin Kofler 2006-03-02 13:19:26 UTC
I just noticed X-Chat in particular being out of date. 
http://www.xchat.org/changelog.txt lists several bugfixes and a few new 
features. 

Comment 3 Peter Zelezny 2006-03-03 02:05:35 UTC
The slow tree-layout in 2.6.0 would be a good reason to go with 2.6.1.

Comment 4 Bryan O'Sullivan 2006-03-03 05:50:02 UTC
2.6.0 is very crashy in rawhide for me, but 2.6.1 is much more stable.

See
http://sourceforge.net/tracker/?func=detail&atid=100239&aid=1441105&group_id=239
for details.

Comment 5 sangu 2006-03-21 11:26:28 UTC
Please update for Korean user.

xchat 2.6.0 has only english messages in ko_KR.UTF-8.
But xchat 2.6.1 display Korean translated messages display in  ko_KR.UTF-8.
http://www.xchat.org/changelog.txt
[...]
2.6.1 - 06/Jan/2006
----------------------------------------------------------------------

 - Updated translations (de, el, fi, fr, gl, hu, ko, nl, pa, sq, vi).
[...]

Comment 6 sangu 2006-04-17 15:38:49 UTC
X-Chat 2.6.2 was released -  Please update to new version. :)

http://www.xchat.org/files/source/2.6/xchat-2.6.2.tar.bz2

Comment 7 Nathan G. Grennan 2006-06-22 23:55:31 UTC
xchat 2.6.4 is out and it has spell checking in the input using Gtkspell. It is
a major feature for me. I was able to recompile with 2.6.4 without a problem. A
build requirement of gtkspell-devel and a requirement of gtkspell should be added.

Comment 8 Remi Collet 2006-07-28 17:23:41 UTC
Created attachment 133252 [details]
xchat-2.6.6-simplify-to-use-gnome-open-for-default-webbrowser.patch

Translations are really missing in 2.6.0.

2.6.6 is out with the translations back (de, el, es, fi, fr, gl, hu, ja, ko,
nl, pa, sq, sr, sv, vi and zh_tw).
Build and work fine on FC5.

Diff from spec file of 2.6.0-4
- remove xchat-2.6.0-dbus-api.patch
- change xchat-2.0.9-simplify-to-use-gnome-open-for-default-webbrowser.patch to
proposal xchat-2.6.6-simplify-to-use-gnome-open-for-default-webbrowser.patch

Thank's for non english speaking users.

Comment 9 Remi Collet 2006-07-29 07:23:03 UTC
Created attachment 133279 [details]
Updated spec file

If it can help : a updated version of the spec file with 
- update to 2.6.6
- new patch for gnome integration
- spell checking enabled.

Comment 10 Peter Zelezny 2006-07-29 15:17:03 UTC
The gnome-open patch is silly. It already uses gnome-open (hardcoded) by default.
The Opera option you removed is only displayed as a further option IF opera is
in your path.

Comment 11 Christopher Aillon 2006-08-04 19:40:11 UTC
We also really ought to get the multiline patch in. 
http://cvs.fedora.redhat.com/viewcvs/devel/xchat/xchat-2.4.4-multiline-messages.patch?rev=1.1&view=auto

Comment 12 Kevin Kofler 2006-08-05 23:35:50 UTC

*** This bug has been marked as a duplicate of 201116 ***


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