[needs-packaging] HexChat
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | xchat |
Fix Released
|
Unknown
|
||
| | xchat (Debian) |
Fix Released
|
Unknown
|
||
| | xchat (Ubuntu) |
Wishlist
|
Unassigned | ||
Bug Description
HexChat originally is a fork of XChat which seems to be inactive, the last version was released on 30th May 2010.
HexChat also has some other improvements: http://
URL: http://
License: GPL v2 (but linking with OpenSSL is allowed)
The source code is being provided via git on GitHub: https:/
| summary: |
- Include XChat-WDK in Ubuntu repositories + [needs-packaging] Please include XChat-WDK |
| Changed in ubuntu: | |
| importance: | Undecided → Wishlist |
| bviktor (bviktor) wrote : | #2 |
Now XChat-WDK is called HexChat. Website:
Announcement:
https:/
Source Code:
https:/
2.9.0 has been released already but it has some serious problems. They have been addressed already, so you should wait at least until 2.9.1. It's expected to be released within a few weeks.
| Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in ubuntu: | |
| status: | New → Confirmed |
| summary: |
- [needs-packaging] Please include XChat-WDK + [needs-packaging] Please include HexChat |
| affects: | ubuntu → xchat (Ubuntu) |
I've setup a PPA with packages of HexChat for releases from Natty to Quantal.
Version 2.9.1 is currently available in it.
It is available there : https:/
Please let me know if you encounter any issues with it.
I think your package should do Provides and Replaces xchat.
Also, your package suffers from bug 933822. You should use this as a base:
https:/
@Daniel Gimpelevich : Thanks, for these remarks.
I've included the patch for bug 933822, I'm now reviewing the other patches in order to include the relevant ones.
About the control file, I think the Provides and Replaces fields should be added in case HexChat gets included in the official Ubuntu repos. As long as the package is only available via PPA, I don't think I should add them.
| Changed in xchat: | |
| status: | Unknown → New |
| summary: |
- [needs-packaging] Please include HexChat + [needs-packaging] HexChat |
| Guest One (g.one) wrote : | #8 |
@Daniel Gimpelevich : i don't think that HexChat can replace XChat because XChat development is not dead.
It must be included in official repositories as a separate package.
@Jeff : All commits to XChat's source code repository are auto-mirrored in HexChat's source code repository. It's a wholesale replacement, and XChat _is_ dead.
2012/10/22 Daniel Gimpelevich <email address hidden>
> @Jeff : All commits to XChat's source code repository are auto-mirrored
> in HexChat's source code repository. It's a wholesale replacement, and
> XChat _is_ dead.
>
@Daniel: can you explain why XChat should be dead?
The latest SVN log is dated *Fri Jul 27 03:07:08 2012 UTC* (2 months, 3
weeks ago) ( from http://
@Jeff: What's the last commit you can find that wasn't also committed to HexChat? Near as I can see, commits to XChat at this point are geared only toward some future Windows binary release, which might not even happen now. There hasn't been a single commit to XChat in 3 months, and the most recent commit to HexChat was just a couple of minutes ago. I can't even scroll back 3 months in its log because of all the commits since.
| no longer affects: | xchat |
| Changed in xchat (Debian): | |
| status: | Unknown → New |
| bviktor (bviktor) wrote : | #12 |
@Jeff: I'm not saying HexChat should replace XChat. Honestly, I don't care much about the XChat package. But adding HexChat would be really nice.
Anyway, have you actually checked out the commits? Last commit: the Tcl maintainer replaced his email address in file headers (this is his first commit in the last 3 years I think). Anything else in the last 2 years comes from the Perl maintainer (or Peter committing a 3rd party patch every year or so), who's the ONLY active committer left. Nobody else has access. The project's basically immutable, there are no managers besides Peter, who does not reply to emails (yeah, not even the ones that come from the Perl maintainer).
| Guest One (g.one) wrote : | #13 |
2012/10/23 bviktor <email address hidden>
> But adding HexChat would be really
> nice...
>
I agree.
So, if XChat is really dead we don't need it anymore and can be replaced by
HexChat; i think that this is a work to do in synchrony with Debian.
| Alchera (barrysuridge) wrote : | #14 |
Ubuntu "precise" 12.04:
2.9.4-0ubuntu3~
| Changed in xchat (Ubuntu): | |
| status: | Confirmed → Triaged |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in xchat: | |
| status: | Unknown → New |
| Changed in xchat: | |
| status: | New → Fix Released |
Sync request asked here
https:/
The package now is in trusty, so closing this "need package" bug.
Now users can choose between xchat and hexchat, as they prefer.
| Changed in xchat (Ubuntu): | |
| status: | Triaged → Fix Released |
| Changed in xchat (Debian): | |
| status: | New → Fix Released |
| Fred (eldmannen+launchpad) wrote : | #17 |
XChat by defaults goes to the network "Ubuntu Servers" which is irc.ubuntu.com which redirects to freenode.
HexChat by default goes straight to freenode.
| Fred (eldmannen+launchpad) wrote : | #18 |
Also XChat has #ubuntu as a favorite channel and marked as default join.
HexChat does not do this.
Having #ubuntu as a marked channel is good for us to build a community.
Fred, you can file that as a bug in the hexchat package. This bug is in the xchat package.


*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https:/ /wiki.ubuntu. com/QATeam/ Specs/NeedsPack agingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.