🦀 apt.cli.rs shut down. Now what?

🧹 First, remove the dead repository

Leaving it configured makes every apt update fail on a host that no longer serves an index. Find the file, whatever it was named, and remove it along with its key:

grep -rl 'cli\.rs' /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null
sudo rm -f /etc/apt/sources.list.d/*cli*rs*.list /etc/apt/sources.list.d/*cli*rs*.sources
sudo rm -f /etc/apt/keyrings/*cli*rs*.gpg /etc/apt/trusted.gpg.d/*cli*rs*.gpg
sudo apt update

grep -rl 'cli\.rs' /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null
rm -f /etc/apt/sources.list.d/*cli*rs*.list /etc/apt/sources.list.d/*cli*rs*.sources
rm -f /etc/apt/keyrings/*cli*rs*.gpg /etc/apt/trusted.gpg.d/*cli*rs*.gpg
apt update

Packages you already installed from it keep working — a .deb does not stop functioning when its repository goes away. They simply stop receiving updates, which is what the rest of this page is about.

📋 Tool by tool

What the official archives ship, checked against upstream on 2026-08-18. Versions move; the shape of the answer does not.

🤔 Why apt.cli.rs stopped making sense

It launched when Debian genuinely had none of these tools. That is no longer the situation: Debian 13 carries almost the whole list, and for most of them the archive version is one or two minor releases behind upstream — close enough that a separate repository is not worth the trust cost. These are mature, slow-moving tools; hyperfine and procs in Debian are within a patch release of upstream today.

That is worth saying plainly even though this is a competing repository's website: if the archive version does what you need, use the archive. It is maintained by people with a security team behind them and it costs you no additional trust. A third-party repository has to earn its place with a gap that actually affects you — a tool the archive does not have at all, or one where the version difference is the difference between working and not.

📦 Where this repository does help

For the five tools above that we build, the difference is cadence: this repository rebuilds within hours of each upstream release, so apt upgrade keeps you on the current version rather than the one frozen at the distro's release date. That matters most for the fast-moving tools — the ones shipping every few weeks — and least for the ones that release twice a year.

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
sudo apt install ripgrep eza zoxide starship fzf

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
apt install ripgrep eza zoxide starship fzf

Every package is built by a public workflow in a public repository — here is exactly how, and how to verify it. From 1 October 2026 downloads need a subscription; there is an always-free mirror and the .deb files stay downloadable from GitHub regardless.

🙋 Want bottom or gitui packaged?

Those two are the real gap: neither is in Debian or Ubuntu, so the only options today are a GitHub release binary or cargo install, and neither updates itself. If you would use them from apt, say so in Discord or open an issue — demand is how the packaging queue gets ordered.

← All packages served by deb.griffo.io