Fresh Builds

The Debian Janitor regularly updates packages from the Debian archive to the latest upstream releases or Git snapshots.

Binary packages that are created as part of this process are made available in an apt repository that can be used on a Debian unstable or testing system.

At the moment, packages are only built for the amd64 architecture. There are 106 source packages with new releases (last published ) and 144 source packages with new snapshots (last published ).


USE AT YOUR OWN RISK. The packages in this repository were created automatically, without review from a human.

Using the repository

To enable the apt repository manually, use:

echo deb "[arch=amd64 signed-by=/usr/share/keyrings/debian-janitor-archive-keyring.gpg]" fresh-snapshots main | sudo tee /etc/apt/sources.list.d/fresh-snapshots.list
echo deb "[arch=amd64 signed-by=/usr/share/keyrings/debian-janitor-archive-keyring.gpg]" fresh-releases main | sudo tee /etc/apt/sources.list.d/fresh-releases.list
sudo curl -o /usr/share/keyrings/debian-janitor-archive-keyring.gpg
apt update

Or, using extrepo:

apt install extrepo
extrepo enable janitor

The repository is marked as experimental, meaning that apt won’t automatically update to packages in them unless explicitly requested to do so. To e.g. install the latest released version of cifs-utils, run:

apt install -t fresh-releases cifs-utils

(Use fresh-snapshots for the latest Git snapshot).

The packages are also versioned in such a way that if the new upstream version gets uploaded to the official Debian APT repository, it will replace the package from this archive.


How do I request a new package to be built?

The easiest way to do this is to go to the fresh-releases or fresh-snapshots pages, browsing to the package you would like to see updated and clicking the "Reschedule" button.

New builds usually take anywhere from a couple of minutes to a few days to become available.

How are these packages tested?

Packages that have Debian autopkgtest tests available are required to successfully pass those tests before they are included in the repository.

Note that not all packages have tests, and where tests exist they may not be comprehensive.

No manual testing has been done on these packages - use at your own risk

How do I trigger updates?

If you maintain an upstream package, you can trigger the building of new snapshots by installing a webhook targeting in your GitHub, GitLab, Gitea, Gogs or Launchpad repository.

The webhook will cause the package for your project to be prioritized for rebuilding.

How are transitions handled?

Today, there is no special handling for transitions.

Can I upgrade all packages to fresh-releases/fresh-snapshots rather than select ones?

This is possible by running something like:

sudo apt dist-upgrade -t fresh-snapshots

However, it is not recommended on anything except test systems - in the same way that you probably want to upgrade to all packages from experimental. You're more likely to hit issues when e.g. upgrading core libraries.

Package list

The following source packages with new upstream releases merged are currently available:

Package Version in Last Release Imported Last Snapshot Imported
certgraph 20180911 20180911
i3-gaps-dotfiles 20200720 20200720
multilockscreen 20200706 20200706
ncat-w32 5.59beta1 5.59beta1
python-icmplib 1.2.2 1.2.2
python-mockito 0.5.2 1.2.0 1.2.0