Downloads
Downloads
quassel-0.5.2
This is the second bugfix release for the 0.5 branch. It mostly contains build system fixes solving problems with recent versions of Qt and KDE, and it allows ignoring CTCP messages as a hotfix for Freenode's recent spam issues (no longer necessary).
Please note that a 0.5 client is not compatible with a 0.4 core, and vice versa. Also, the database schema and config file format have been updated. We recommend making backups before starting your 0.5 core or client for the first time. Also remember that downgrades are not supported.
If you do not want to upgrade to 0.5 yet (e.g. because you're using a distribution that doesn't allow such updates during release cycles), we heavily recommend using quassel-0.4.3 at least, as this contains many bugfixes over older versions. Note that the 0.4 branch is now EOLed; there won't be new releases for it.
Source:
Our source tarball contains the source code for all platforms.
Distribution Packages
Packages for various *buntu versions are available, thanks to ScottK.
Gentoo users can simply emerge net-irc/quassel (thanks Flameeyes, jokey, billie, bonsaikitten, scarabeus!).
Quassel is also available in Debian (thanks deepdiver), OpenSUSE, Fedora, Arch (kudos to vegai), Exherbo and other distros; the new release should appear soon. Fink users on Mac can obtain an X11 version of Quassel via the unstable package repository, packaged by jack-. Note that we also provide precompiled native MacOSX binaries (see below).
If you would like to provide packages for your distribution, please contact us!
Precompiled versions:
- Statically linked core for Linux/x86 systems.
This core does not require Qt or SSL installed and should run out-of-the-box on most current Linux systems on x86 or x86_64 (with 32 bit emulation support). - Mac OS X (universal binary) Client
- Mac OS X (universal binary) Core
- Static client executable for Windows XP, Vista and 7
- Static core executable for Windows XP, Vista and 7
- Static monolithic client executable for Windows XP, Vista and 7
(This contains both core and client and can be used like a traditional IRC client, without requiring an external core.)
Static binaries contain everything they need to run and don't require Qt to be installed.
Development Snapshot Builds
We provide binaries of development snapshots on a regular basis: statically linked core for Linux, MacOSX client binaries and Windows binaries. For pure Linux 64 bit systems (i.e., without 32 bit emulation), Jannik now provides experimental static x86_64 cores. Datafreak has automated hourly builds for Windows.
You can get a source tarball of current git master or of any other revision via gitweb.
Please be aware of the fact that these binaries are generated automatically from the current master branch of the Git repository, which means they might be in an untested and/or non-working state and possibly screw your config. See below for even more disclaimers.
Git Access
Our Git repository can be accessed by pointing your browser to http://git.quassel-irc.org?p=quassel.git. Or you might clone the repository as follows:
git clone git://git.quassel-irc.org/quassel.git
Please note that code you get from this repository is not intended for productive use (unless it's tagged as a released version, of course, in which case the usual alpha/beta disclaimers apply ;-)). We like to break our codebase, config files, database schemas and all kinds of stuff. We sometimes commit non-compiling revisions to facilitate collaborative development. Running such an unstable version might trash your settings, your backlog and maybe your computer. You have been warned!
Please note also that we still tweak and break the core/client protocol on a regular basis. This means that your client sometimes will require a certain core revision and the other way round. Both client and core will warn in this case and refuse the connection, but you should be aware of that fact anyway (especially since downgrades of config files or the database are usually not possible, so trying a client or core that is "too new" and auto-upgrades your config might require you to upgrade the other component as well!)
That said, we do try to keep git master in a neat and working state, and normally take care about it compiling and working at all times. We have many users regularly building from git, so any issues that arise are usually fixed quickly.
If you are still interested, you might always stop by in #quassel (Freenode) and ask us for the current state or a stable revision.

Recent comments
8 hours 59 min ago
9 hours 19 min ago
11 hours 29 min ago
15 hours 57 min ago
15 hours 58 min ago
15 hours 59 min ago
3 weeks 9 hours ago
5 weeks 4 days ago
11 weeks 14 hours ago
15 weeks 5 days ago