📊 Debian 13 and Ubuntu package versions

📋 The table

Official versions come from the Debian and Ubuntu archives themselves (the madison service), compared against the current stable release of each: Debian 13 “Trixie” and Ubuntu 26.04 “Resolute”. Backports, testing and unstable are excluded, the question is what a stock stable system gives you. The last column is what this repository serves today.

Versions are half the question; whether a package is built for your machine at all is the other half. The full package × architecture matrix →

🔍 How to read it

• “not packaged” means the archive has no package of that name at all, in that distribution's current stable release. On a stock system apt install fails with “Unable to locate package”.
• Versions are printed as the archives report them, with epochs and Debian revisions stripped, so 1:0.44.1-1ubuntu2 reads as 0.44.1: the number the upstream project would recognise.
• A tool can be in Ubuntu but not Debian, or the reverse: the two archives make independent decisions and freeze on different dates.
• Nothing here is a criticism of Debian. A frozen archive is what makes a stable release stable, and for a great many packages that is exactly what you want. It is a poor fit for tools that ship every few weeks, which is the entire reason this repository exists.

✅ Check any row yourself

Every number above is public. On a Debian or Ubuntu machine:

apt-cache policy ripgrep        # what your system would install, and from where
apt-cache madison ripgrep       # every version your configured sources offer
rmadison ripgrep                # what the official archives ship, without installing anything

rmadison comes from the devscripts package and queries the same service this table is built from. The deb.griffo.io column tracks each project's newest release, rebuilt within hours of it; every tool's packaging repository is listed on how packages are built.

📦 Getting the current version instead

One repository line covers every tool in the table, rebuilt within hours of each upstream release:

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.griffo.io/EA0F721D231FDD3A0A17B9AC7808B4DD62C41256.asc | sudo gpg --dearmor --yes -o /etc/apt/keyrings/deb.griffo.io.gpg
echo "deb [signed-by=/etc/apt/keyrings/deb.griffo.io.gpg] https://deb.griffo.io/apt $(lsb_release -sc 2>/dev/null) main" | sudo tee /etc/apt/sources.list.d/deb.griffo.io.list > /dev/null
sudo apt update

install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.griffo.io/EA0F721D231FDD3A0A17B9AC7808B4DD62C41256.asc | gpg --dearmor --yes -o /etc/apt/keyrings/deb.griffo.io.gpg
echo "deb [signed-by=/etc/apt/keyrings/deb.griffo.io.gpg] https://deb.griffo.io/apt $(lsb_release -sc 2>/dev/null) main" | tee /etc/apt/sources.list.d/deb.griffo.io.list > /dev/null
apt update

sudo apt install extrepo
sudo extrepo enable griffo
sudo apt update

It is not the only answer, and for a tool your distribution already ships at a version that does what you need, the archive remains the better choice. It costs no additional trust. That argument, in full →

← All packages served by deb.griffo.io