I am using git for version control, and my repositories are hosted at http://git.liw.fi. Debian apt repositories, release tarballs, etc, are at http://code.liw.fi/debian. Home pages for projects are mostly on http://liw.fi.

Release tarballs

I do not currently provide release tarballs, except as part of building a Debian package. To find those tarballs, browse http://code.liw.fi/debian/pool/main/.

To check the validity of the tarballs, use the usual Debian tooling to follow a signature path from the the Release.gpg and Release files. The Release file contains the checksum of the Packages file, which contains the checksums of the invidiual package file, including the source tarball.

Some day I will provide signed tarballs directly, but that'll have to wait for me to re-invent my release process.

The Debian repository

I maintain an apt repository with packages for my personal projects. I use the packages myself, and I often depend on them, so they usually work for me. I only provide packages for amd64 and i386 architectures. I currently support Debian stable and unstable, and usually also oldstable.

You're welcome to use the repository. To do so, add one of the following to your sources.list file:

deb http://code.liw.fi/debian wheezy main
deb http://code.liw.fi/debian jessie main
deb http://code.liw.fi/debian unstable main

The PGP key that is used to sign the Release files is at


I have signed the key with my personal key, so you can verify it using the usual Web of Trust mechanisms.

The archive signing key is also provided in the code.liw.fi-keyring package. I encourage you to install that package. This helps, when I switch package signing keys: I will add the new key to the package ahead of time, and so you shouldn't ever need to even notice the change.

Bug trackers

I use distix for bug tracking. The web view of tickets is at http://bugs.liw.fi/. To send mail to distix, mail to bugs at my domain. Specific programs may have their own ticketing systems. If so, their home pages mention that.