duckdb 1.5.5-1~forky for forky
(updated 2026-08-17) — architectures: amd64, arm64. This page is regenerated automatically from the
repository metadata, so the version above is exactly what apt install duckdb gives you today.
Debian 14 “Forky” is the current Debian testing release. DuckDB is not shipped at its latest version by the official Debian archives,
so this repository builds current upstream releases as native .deb packages targeted
specifically at forky, with dependencies matching what Debian 14 actually ships.
And then it keeps doing it. Every new upstream release is packaged and published
here within hours, so DuckDB updates arrive the same way your system updates do — through
apt upgrade, unattended-upgrades, or whatever already runs on your machine. No release
page to watch, no version to compare, no dpkg -i to remember.
🚀 Install DuckDB on forky
Step 1: Add the deb.griffo.io repository
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 forky main" | sudo tee /etc/apt/sources.list.d/deb.griffo.io.list > /dev/null
sudo apt updateinstall -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 forky main" | tee /etc/apt/sources.list.d/deb.griffo.io.list > /dev/null
apt updateThe sources line above pins the forky suite explicitly, so it keeps working
in containers and images where lsb_release is unavailable.
Step 2: Install DuckDB
sudo apt install -y duckdbapt install -y duckdb🔄 Updating
Updates arrive through normal system maintenance — new upstream releases are usually packaged within hours:
sudo apt update && sudo apt install --only-upgrade duckdbapt update && apt install --only-upgrade duckdb🗑️ Uninstalling
sudo apt remove duckdb
# optionally remove the repository as well:
sudo rm /etc/apt/sources.list.d/deb.griffo.io.list /etc/apt/keyrings/deb.griffo.io.gpgapt remove duckdb
# optionally remove the repository as well:
rm /etc/apt/sources.list.d/deb.griffo.io.list /etc/apt/keyrings/deb.griffo.io.gpg📋 DuckDB versions across Debian & Ubuntu releases
The same repository serves every supported release — this table is generated from the live repository metadata:
| Release | Suite | DuckDB version |
|---|---|---|
| Debian 12 “Bookworm” | bookworm | 1.5.5-1~bookworm |
| Debian 13 “Trixie” | trixie | 1.5.5-1~trixie |
| Debian 14 “Forky” | forky (this page) | 1.5.5-1~forky |
| Debian Sid | sid | 1.5.5-1~sid |
| Ubuntu 22.04 LTS “Jammy Jellyfish” | jammy | 1.5.5-1~jammy |
| Ubuntu 24.04 LTS “Noble Numbat” | noble | 1.5.5-1~noble |
| Ubuntu 25.10 “Questing Quokka” | questing | 1.5.5-1~questing |
| Ubuntu 26.04 LTS “Resolute” | resolute | 1.5.5-1~resolute |
❓ Frequently asked questions
Is this an official DuckDB package?
No — deb.griffo.io is an unofficial repository maintained by Dario Griffo. Packages are built automatically from official upstream DuckDB releases; the packaging is open source at dariogriffo/duckdb-debian.
Why not install DuckDB from the official Debian archive?
Debian's archive freezes package versions when a release ships and afterwards receives mostly security fixes, so fast-moving tools are either absent or several releases behind. This repository tracks upstream releases instead, with builds targeted at each Debian release.
How quickly do new DuckDB releases arrive?
The repository polls upstream releases and publishes new builds automatically, typically within hours of an upstream release. Subscribe to the release feed to follow updates.
Which architectures are supported on forky?
duckdb is currently built for: amd64, arm64.
🔗 Related
- DuckDB on Debian — overview and features
- garage — same category (storage)
- tigerbeetle — same category (storage)
- All packages served by deb.griffo.io