Debian is a community-developed Linux distribution, founded in 1993, that combines the Linux kernel with GNU tools and tens of thousands of software packages into a complete operating system. It is known for conservative, thoroughly tested stable releases, the APT and dpkg package management system and a formal commitment to free software expressed in the Debian Social Contract.
Among Linux fundamentals, Debian matters both directly and as a foundation. It runs on servers, desktops and embedded devices, and it is the upstream base for many other distributions, most prominently Ubuntu. Knowing how Debian is organized, released and maintained explains the behavior of a large share of the Linux systems in use.
How the Debian project is organized
Debian is produced by a volunteer organization rather than a company. Around a thousand official developers, plus many more contributors, maintain packages, build infrastructure and documentation. The project elects a Project Leader each year, and technical disputes can go to a Technical Committee. Its governance is defined in the Debian Constitution.
Two documents shape its software choices. The Debian Social Contract commits the project to remaining entirely free software and to serving its users, and the Debian Free Software Guidelines (DFSG) define which licenses qualify. These guidelines later served as the basis of the widely used Open Source Definition.
The package archive is divided into areas that reflect these rules, as the table shows.
| Area | Content | Officially part of Debian |
|---|---|---|
| main | Software that meets the DFSG and depends only on main | Yes |
| contrib | Free software that depends on non-free components | No |
| non-free | Software with restrictive licenses | No |
| non-free-firmware | Device firmware needed by much hardware | No, but included on installation media since Debian 12 |
Debian branches and the release cycle
Debian maintains several suites at the same time. New packages enter unstable, permanently code-named sid, and migrate to testing after a waiting period of usually a few days if no serious bugs are reported. When testing is frozen and its release-critical bugs are fixed, it becomes the new stable release. Releases are named after characters from the Toy Story films, such as bookworm for Debian 12 and trixie for Debian 13.
| Branch | Change rate | Typical use |
|---|---|---|
| stable | Security and important fixes only | Servers and production systems |
| testing | Continuous updates, no security guarantees | Developers and early adopters |
| unstable (sid) | Newest packages, occasional breakage | Package maintainers and contributors |
| experimental | Not a full distribution | Trial versions of specific packages |
| backports | Newer versions rebuilt for stable | Selected updates on stable systems |
A new stable release appears roughly every two years. Each release receives full security support for about three years, and the separate Debian LTS effort extends support for common architectures to about five years in total. Point releases every few months bundle accumulated fixes without changing major versions.
Package management in Debian
Software in Debian is distributed as .deb packages. The low-level tool dpkg installs, removes and inspects individual package files, while APT resolves dependencies, downloads packages from repositories and verifies them with cryptographic signatures. Administrators usually interact with the apt command, for example apt update followed by apt upgrade.
Debian packaging follows a detailed Debian Policy Manual, which governs file locations, configuration handling and maintainer scripts. This policy is why configuration files under /etc are preserved across upgrades and why the system can usually be upgraded in place from one stable release to the next.
The same archive is built for multiple processor architectures, including amd64, arm64, armhf, ppc64el and s390x, which explains Debian’s popularity on single-board computers and mainframes alike. Debian also invests in reproducible builds, a practice that lets anyone verify that a binary package was produced from its published source code without hidden modifications.
Debian compared with related distributions
Debian is often contrasted with other major distribution families. The table summarizes the differences that most influence a practical choice.
| Distribution | Governance | Release model | Package format |
|---|---|---|---|
| Debian | Volunteer community | Stable releases about every two years | deb with APT |
| Ubuntu | Company-led, derived from Debian | Twice yearly, LTS every two years | deb with APT, plus snaps |
| Fedora | Community with corporate sponsor | About every six months | RPM with DNF |
| Arch Linux | Volunteer community | Rolling release | pacman packages |
The main trade-off is stability against freshness. Debian stable deliberately ships versions that are well tested rather than the newest, which suits long-running servers but can frustrate users who need recent desktop applications or hardware support. Backports, containers and language-specific package managers are the usual ways to bridge that gap.
Practical considerations and common mistakes
The most damaging mistake is creating a mixed system by adding repositories from other branches or from Ubuntu to a stable installation. Packages built for different library versions can conflict, and the result is often called a FrankenDebian, a system that is hard to upgrade and support. Backports are the supported way to obtain newer versions.
- Enable the security repository and apply updates regularly, ideally with unattended upgrades for security fixes.
- Read the release notes before a major upgrade; they list removed packages and required manual steps.
- Upgrade one stable release at a time, never skipping a version.
- Plan migrations before the end of LTS support, because unsupported systems no longer receive security fixes.
In simple terms
Debian is a free operating system built by volunteers around the world. It collects thousands of programs, tests them together and delivers them as one carefully checked package.
Its best-known quality is reliability over novelty. Debian prefers well-tested software to the very latest versions. That is why many companies run their servers on it for years, and why other systems, such as Ubuntu, start from Debian and build on top of it.
A practical example
A regional hosting provider runs about 300 virtual servers for customer websites on Debian stable. Security updates install automatically every night, while larger changes go through a monthly maintenance window. Because each stable release is supported for several years, the provider can plan major upgrades once every two years instead of chasing frequent version changes.
When a new stable release appears, the team waits for the first point release, tests its own configuration on a few staging servers and reads the release notes. It then upgrades servers in groups of twenty. The in-place upgrade takes under an hour per group, and customer websites keep their configuration because Debian preserves modified files under /etc.