Quassel 0.12.5

0.12.x clients are compatible to cores starting from 0.5.x and vice versa. Note, however, that you won't get some features with an outdated core, and that you might get (a lot of) (harmless) warnings spammed on your console if you mix old and new versions. Also, the new and more efficient DataStream protocol is only available if both ends run at least 0.10.x.

The database schema and config file format are usually updated between minor releases (e.g. 0.11.1 -> 0.12.5). As always, we recommend making backups before starting your updated core or client for the first time. Also remember that downgrades to a previous minor release are not supported.
Between patch releases (e.g. 0.12.4 -> 0.12.5), we don't usually change config file formats or the database schema, so downgrades within the same minor release should usually work.


Our source tarball contains the source code for all platforms.

Distribution Packages

Packages for various *buntu versions are available, thanks to ScottK, Riddell and apachelogger.
Gentoo users can simply emerge net-irc/quassel (thanks Flameeyes, johu, jokey, billie, bonsaikitten, scarabeus!).
Quassel is also available in Debian (thanks deepdiver, debfx, ScottK), OpenSUSE, Fedora, Arch (kudos to vegai), Exherbo and other distros; the new release should appear soon if it's not there yet.

Michael Marley provides a PPA containing the latest Quassel release for *buntu Trusty and up.

If you would like to provide packages for your distribution, please contact us!

Precompiled versions
  • Pesudo-statically linked core for Linux/x86 systems.
    This core does not require Qt or PostgreSQL to be installed and should run out-of-the-box on most current Linux systems on x86 or x86_64 (with 32 bit emulation support). Some libraries, such as libc and OpenSSL, are still linked against dynamically and thus must be available on the system.
  • OSX Core
  • OSX Client (requires a separate core)
  • OSX Monolithic Client (all-in-one, standalone client)
  • Windows installer (32 bit, 64 bit) containing core, client and the standalone client.

Neither OSX packages nor Windows builds support the PostgreSQL storage backend, both due to technical limitations in our build tooling and lack of demand.

Development Snapshot Builds

Some of our users provide binaries of development snapshots on a regular basis:

Please be aware of the fact that these binaries might be 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 and Contributions

Our main repository is located at Github. Contributions are very welcome, and preferred in the form of pull requests on Github.

The code you get from this repository is not intended for productive use. We sometimes break things or commit experimental features. However, we do try to keep the master branch in a usable and compiling state most of the time, as we have many users building from that despite all our disclaimers ;-) Breakages usually get reported very quickly.

Please note however that we might upgrade configuration files or the database scheme without prior notice, and you may not be able to run older versions afterwards, as we don't support downgrades. Sometimes we might upgrade the core/client protocol, so you won't be able to use a stable client with an experimental core or vice versa. You have been warned!

Please note also that we still tweak and break the core/client protocol sometimes. 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!)

If you are still interested, you might always stop by in #quassel (Freenode) and ask us for the current state or a stable revision.