To use our repositories, follow the instructions below: Set up the APT configuration and import our signing key.

Add any applicable source entries to /etc/apt/sources.list.d/bunsen.list:

Maintained1 Release(s) Repository Architectures2 sources.list entry Index
Lithium lithium amd64, i386, armhf, arm64 deb lithium main
Lithium buster-backports amd64, i386 deb buster-backports main
Helium helium deb helium main
Helium stretch-backports deb stretch-backports main
Hydrogen, Deuterium jessie-backports deb jessie-backports main
Hydrogen, Deuterium bunsen-hydrogen deb bunsen-hydrogen main


We currently operate two repository mirrors. If you specify the host in your APT configuration, you will be redirected automatically to the preferred server based on your IP addresses geolocation:

If you get redirected to but notice that your ISP has a faster route to the EU server than the Singapore one, put into your APT configuration in order to opt out from the redirect. Similarly, users in Europe, the Americas or Africa for whom is faster should switch to that mirror.

Access via HTTPS

You may change the http:// prefix in your BL repository URLs to https:// in order to access the repositories using an encrypted connection. Before setting this up, ensure that the package apt-transport-https is installed on your system. The package is part of the BL standard installation.

You might see apt-get update complaining sporadically with the error: W: Size of file [...] is not what the server reported. apt has some strange issues in conjunction with apt-transport-https which are hard to debug despite having been declared fixed before (e.g. Debian bug #802617). As a workaround, either ignore the messages or do not use apt-transport-https.

Signing key

The preferred method for installing our archive key on your system is using the provided keyring package.

Keyring package

  1. Select and download the latest bunsen-keyring package for your distribution.
  2. Install the package:
sudo dpkg -i $package
sudo apt-get update

Manual setup

Fetch and verify the repository’s signing key:

The key’s fingerprint as displayed by gpg should be identical with the following hexstring:

3172 4784 0522 7490 BBB7 43E6 A067 3F72 FE62 D9C5 

If that is not the case, you have got the wrong key. Use a safe, non-intercepted internet connection in order to retrieve the correct key file.

Finally, add the key to APT and update the package index:

You may now install bunsen-* packages provided by the repository.

  1. This means that the distribution will receive updates if bugs are found (our own packages only) or new upstream releases are available (software developed by third parties). As a general rule, distributions named after our releases that are maintained will receive bugfixes and software updates regularly, while ‘backports’ repositories are updated on a best-effort basis.

  2. All binary packages in this repository will be available at least for the given architectures. However, all but amd64 and i386 are maintained on a best-effort basis and may get dropped at some point. Empty lines in this column just mean I didn’t want to go through old repositories and check every package.