Skip to content
@latest-debs

Latest .deb packages Initiative

Making Debian packaging fast and easy — latest stable developer tools as .deb packages, served over apt, refreshed within hours of each upstream release.

latest-debs

latest-debs

Latest stable releases of developer tools, packaged as .deb and served over apt.
Debian freezes package versions for years. We track upstream and publish new releases within hours —
and we've made the Debian packaging itself fast and easy, so any team can do the same.

websiterequest a packagediscussionssponsor


The problem with dev tools on Debian

Debian stable is an excellent base — but its packages freeze at release time and stay frozen for years. Developer tools move far faster, often releasing weekly, so the versions shipping in apt are routinely months or years behind upstream. Every common workaround trades away something real:

Today's workaroundThe catch
Wait for Debian stableYears behind; missing features and fixes
Run Sid, or pull from testing/backportsSee below — Sid solves a different problem
curl … | sh install scriptsNo signature verification, no upgrades, no clean uninstall
Ad-hoc third-party reposOften single-arch, unsigned, silently abandoned
cargo install / pipx / manual buildsNeeds a toolchain; no system-wide updates; you become the packager
Snap / FlatpakExtra runtime and sandboxing overhead for a simple CLI

"But Debian Sid already has fresh packages — what are you solving?" Sid is a full rolling development branch: every package on your system moves, all the time. It's the right base for working on Debian itself, and the wrong base for a workstation or server you depend on. Installing a single tool from Sid onto stable usually drags in a newer glibc and half the toolchain with it. And even Sid trails upstream — maintainer upload cycles, NEW-queue reviews, and release freezes regularly add weeks of lag.

What we're solving is deliberately narrower: keep Debian stable as your OS, and get just your dev tools at upstream speed — built as proper packages for the stable suites, so nothing else on your system has to move.

latest-debs exists to close that gap. We do proper Debian packaging of upstream releases in fully public CI and publish to a signed apt repository — so apt install and apt upgrade just work, across every architecture each upstream actually ships for Linux, within hours of each upstream release. Native packages, native tooling, no compromises.

The Mission

Make Debian packaging fast and easy.

Shipping software for Debian shouldn't require becoming a Debian packager — yet today it does: debhelper, Policy, control/rules files, multi-arch builds, signing, repo hosting. A steep, time-consuming detour when you just want to ship a CLI. Most developers, teams, and orgs skip .deb entirely, and their Debian users pay for it in curl | sh scripts and stale copies.

latest-debs removes that cost:

  • One reusable builderdebian-multiarch-builder, a GitHub Action that turns an upstream release into signed, multi-arch .deb packages in a single workflow run. No packaging expertise required.
  • Distribution included — releases flow into this signed apt repo automatically. Nothing to host, sign, or babysit.
  • Open to your tool — open a package request, or add it to tools.yaml in a PR. Every future upstream release then ships as a .deb within hours.

Everything in this org is built with that same pipeline — the repo is the demo as well as the product.

New here? Start in 30 seconds

On Debian (Bookworm or Trixie), with extrepo:

sudo extrepo enable latest-debs
sudo apt update
sudo apt install uv eza lazygit ruff bun deno duckdb lazydocker

Or add the repository manually:

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://raw.githubusercontent.com/latest-debs/apt-repo/main/latest-debs.asc \
| sudo gpg --dearmor --yes -o /etc/apt/keyrings/latest-debs.gpg
echo"deb [signed-by=/etc/apt/keyrings/latest-debs.gpg] https://latest-debs.github.io/apt-repo/ $(lsb_release -sc) main" \
| sudo tee /etc/apt/sources.list.d/latest-debs.list
sudo apt update

Status: early days, but working. All four suites (Bookworm, Trixie, Forky, Sid) are live and signed today. The catalog grows one request at a time — 24 tools and counting.

Packages

ToolWhat it isLatest .debInstall
uvExtremely fast Python package & project managerreleasesudo apt install uv
ezaModern, maintained ls replacementreleasesudo apt install eza
lazygitSimple terminal UI for gitreleasesudo apt install lazygit
ruffExtremely fast Python linter & formatterreleasesudo apt install ruff
bunFast all-in-one JavaScript runtime & toolkitreleasesudo apt install bun
denoModern runtime for JavaScript & TypeScriptreleasesudo apt install deno
duckdbAnalytical in-process SQL databasereleasesudo apt install duckdb
lazydockerThe lazier way to manage everything dockerreleasesudo apt install lazydocker
ripgrepRecursively search directories for a regex patternreleasesudo apt install ripgrep
fdSimple, fast alternative to findreleasesudo apt install fd
fzfCommand-line fuzzy finderreleasesudo apt install fzf
starshipMinimal, fast, customizable shell promptreleasesudo apt install starship
justHandy command runnerreleasesudo apt install just
hyperfineCommand-line benchmarking toolreleasesudo apt install hyperfine
k9sKubernetes CLI to manage your clusters in stylereleasesudo apt install k9s
atuinMagical shell historyreleasesudo apt install atuin
xhFriendly and fast tool for sending HTTP requestsreleasesudo apt install xh
yqPortable command-line YAML, JSON & XML processorreleasesudo apt install yq-go
dustA more intuitive version of dureleasesudo apt install du-dust
procsA modern replacement for psreleasesudo apt install procs
bottomCross-platform graphical process/system monitorreleasesudo apt install bottom
batA cat(1) clone with wingsreleasesudo apt install bat
zoxideA smarter cd command for your terminalreleasesudo apt install zoxide
deltaSyntax-highlighting pager for git, diff, grep & blamereleasesudo apt install git-delta

yq and delta/dust ship under the names yq-go/git-delta/du-dust — Debian's own archive already has unrelated packages under their plain names, so ours are disambiguated the same way upstream (or other distros) already do.

Want another tool packaged? Request it — that's how the list grows. Track all open requests under the package-request label.

Supported systems

  • Debian: Bookworm (12), Trixie (13), Forky (14/testing), and Sid (unstable) — all live
  • Architectures: amd64, arm64, armhf, armel, i386 (Bookworm/Trixie only), ppc64el, riscv64, s390x, loong64 — whichever each upstream actually publishes a Linux build for (not every tool covers all nine; see each package's repo for its exact list)
  • Updates: the repo rebuilds automatically, roughly every 6 hours after an upstream release

Ubuntu and derivatives are not officially targeted yet — the packages may install fine, but they're only tested on Debian.

Trust & verification

All packages are built in public GitHub Actions runs from public upstream sources — no blobs, no private steps. The apt repo is signed with:

ed25519 9329 C48E AEC0 0249 5619 50D4 C34D 4229 518A B96A
uid latest-debs <latest-debs@users.noreply.github.com>

Verify the key you downloaded before enabling the repo:

gpg --show-keys /etc/apt/keyrings/latest-debs.gpg

Every build is produced by debian-multiarch-builder, a reusable GitHub Action you can inspect and reuse.

Where things live

RepoPurpose
apt-repoThe aggregate apt repository: signing key, pool/, dists/, build scripts, and the tool registry (tools.yaml)
<tool>-debian (one per package)Per-tool packaging and multi-arch .deb releases — see the Latest .deb column in the Packages table above for each one
latest-debs.github.ioThe landing page at latest-debs.github.io
.githubThis profile and org-wide defaults
debian-multiarch-builderThe reusable GitHub Action every <tool>-debian repo builds with

FAQ

Is this official Debian? No — unofficial, community packaging. For issues with a tool itself, report upstream; for packaging issues, open an issue on the tool's -debian repo.

How fresh are the packages? A scheduled workflow checks upstream releases and rebuilds; expect new versions within ~6 hours of the upstream tag.

How do I add my favorite tool? Open a package request — name, upstream URL, and license is all we need. Or add an entry to tools.yaml in a PR against apt-repo.

Contributing & support

Outreach is the thing we need most right now — the tooling works and the packages exist; what's missing is people bringing them to the projects and developers who'd benefit. If you'd like to sign up for outreach — pitching the packaging service to a project's maintainers, driving package requests, writing about the project, or fielding questions in discussions — see CONTRIBUTING.md.

Packaging fixes, new tools, and build-config reviews are also welcome — see apt-repo for how the pipeline works. If latest-debs saves you time, sponsor the automation.

Popular repositories Loading

  1. .github .githubPublic

    latest-debs org profile

  2. apt-repo apt-repoPublic

    Latest dev-tool .debs served over apt for Debian

    Shell

  3. uv-debian uv-debianPublic

    uv (Python package manager) .deb packages for Debian

  4. eza-debian eza-debianPublic

    eza (modern ls) .deb packages for Debian

  5. lazygit-debian lazygit-debianPublic

    lazygit (terminal git UI) .deb packages for Debian

  6. latest-debs.github.io latest-debs.github.ioPublic

    latest-debs landing page & org Pages site

    HTML

Repositories

Showing 10 of 43 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…