Packages / htop
APT repository · deb.freshdeb.com/htop
htop
htop, the interactive process viewer. Processes, CPU, memory and I/O at a glance, with sorting, filtering, a tree view and signals from the keyboard or mouse. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.
latest 3.5.3htop.devupstream sourcepackaging
Componentmain
follows every upstream release, minors and majors included. Currently 3.5.3.
Not published yet. The first htop release is being built. These commands will work once it lands at deb.freshdeb.com/htop; the versions shown are the ones package.yaml will publish.
1Trust the signing key (once per machine)
sudo install -d -m 0755 /etc/apt/keyrings curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \ | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null
Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.
2Add the source
sudo tee /etc/apt/sources.list.d/freshdeb-htop.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/htop
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOFWith auto, the shell reads the codename from /etc/os-release on the machine you paste this into.
3Install
sudo apt update && sudo apt install htop
apt policy htop # expect 3.5.3-1+freshdeb~…Already on the distribution's htop? The freshdeb version sorts higher, so apt upgrade moves you over in place. Config and data stay where Debian put them.
Compared with Debian's package
Debian's packaging decides where things go: package names, paths, users, services and how upgrades behave. The build follows upstream's own release builds wherever Debian's differs.
- Build
- Debian's packaging, unchanged, from upstream's release tag. It patches nothing upstream and builds with CPU affinity, delay accounting, backtraces, sensors and Unicode support.
- Layout
- Debian's:
/usr/bin/htop, with your settings in~/.config/htop/htoprckept as they are.
Packing list
Every release line of htop and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.
| Line | Component | Current | bookwormDebian 12 | trixieDebian 13 | jammyUbuntu 22.04 | nobleUbuntu 24.04 | resoluteUbuntu 26.04 | Support |
|---|---|---|---|---|---|---|---|---|
| main | main | 3.5.3 | built: 3.5.3-1 | built: 3.5.3-1 | built: 3.5.3-1 | built: 3.5.3-1 | built: 3.5.3-1 | – |
Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.
Contents
- htop
- The process viewer.
Origin
- Upstream
- github.com/htop-dev/htoprelease tags pinned to commit hashes
- Debian packaging
- salsa.debian.org/debian/htopimported unmodified at be7ad56 (3.5.3-1, unstable)
- Built for
- bookworm, trixie, jammy, noble, resoluteamd64, arm64, built natively
- Files
- package.yaml · debian/ · report an issuepackage.yaml explains every change
