Upgrade to Debian 12 Bookworm from Debian 11

Yes, you can upgrade from Debian 11 (Bullseye) to Debian 12 (Bookworm), and the process is fully supported by the official Debian release notes. The upgrade is straightforward for most systems, but it requires careful preparation, a full backup, and attention to a few known issues.

What Changed in Debian 12

Debian 12 Bookworm was released on June 10, 2023, after about two years of development. It ships with Linux kernel 6.1 LTS, GCC 12, and over 64,000 packages. The most visible changes include:

Newer desktop environments: GNOME 43, KDE Plasma 5.27, Xfce 4.18, and Cinnamon 5.4.
Default file system for new installations is now ext4 with optional LUKS2 encryption (no more LUKS1 for new installs).
Non-free firmware is now included in the standard installation images, making hardware support easier.
OpenSSL 3.0 replaced OpenSSL 1.1, which may affect some third-party software.

Most user-facing applications look and behave similarly, but the underlying system libraries are significantly newer.

Before You Start: Backup and Preparation

Upgrading a Debian system is generally reliable, but a failed upgrade can leave you with an unbootable system. The single most important step is a full backup of your data and configuration files. The official Debian documentation stresses this repeatedly.

You should back up:

All user files in /home (or at least the ones you cannot recreate).
Configuration files in /etc (especially /etc/apt, /etc/fstab, and any service-specific configs).
Any databases, mail spools, or web server data.
Output of dpkg --get-selections to restore package lists if needed.

Also, ensure you have at least 2–3 GB of free disk space (more if you have many packages) and a stable internet connection. If you are using a laptop, keep it plugged in. A power loss during the upgrade can corrupt the system.

Step-by-Step Upgrade Process

The upgrade process is the same as for previous Debian releases. You will do it in two phases: first, update to the latest Debian 11 point release, then change the apt sources to Bookworm and run the upgrade.

Update your current Bullseye system:
sudo apt update && sudo apt upgrade
Then run sudo apt full-upgrade to ensure all packages are at the latest Bullseye versions.
Edit your apt sources file. The file is usually /etc/apt/sources.list or in /etc/apt/sources.list.d/. Replace every occurrence of bullseye with bookworm. For example, change deb http://deb.debian.org/debian bullseye main to deb http://deb.debian.org/debian bookworm main.
Run sudo apt update to refresh the package lists. You may see warnings about repositories that no longer have a Release file; that is normal if you missed a component.
Run sudo apt full-upgrade. This is the core of the upgrade. It will download and install all new packages, and it will ask you questions about configuration files (e.g., for services like ssh or cron). Read each prompt carefully and choose the default unless you know what you are doing.
After the upgrade finishes, run sudo apt autoremove to remove obsolete packages, and sudo apt --purge autoremove to also remove their config files.
Reboot your system. If everything went well, you will boot into Debian 12. Verify with cat /etc/debian_version (should show 12.x) or lsb_release -a.

If you use a graphical desktop, you can also use the GUI package manager (Synaptic or the Software Center) to perform the upgrade, but the command line is more reliable and gives you more control.

Common Problems and How to Fix Them

Most upgrades go smoothly, but a few issues are common enough to mention:

Held packages: Sometimes apt refuses to upgrade because a package is “held back.” This often happens with proprietary drivers or packages from third-party repositories. Check with apt-mark showhold and unhold them if appropriate, or remove the third-party repo before upgrading.
Configuration file prompts: During the upgrade, dpkg will ask what to do with configuration files that have local modifications. The safe choice is usually “keep the local version” unless you know the new version is required. If you choose to replace, you can often find the old version in .dpkg-old files.
Services that fail to restart: After the upgrade, some services may not restart automatically. Check with systemctl --failed and restart them manually.
Network issues: If you lose network connectivity after the upgrade, check that the correct firmware packages are installed (especially for Wi-Fi). Debian 12 includes non-free firmware in the standard images, but if you upgraded from an older install, you may need to add the non-free-firmware component to your sources.
Boot problems: If the system fails to boot, you can use a Debian 12 live USB to chroot into your installed system and fix issues. The Debian wiki has detailed instructions for this.

If you encounter a problem, the first place to look is the official Debian 12 Release Notes, which list known issues and their solutions.

Comparison: Fresh Install vs. Upgrade

Many users wonder whether they should upgrade in place or do a fresh install. Both are valid, and the choice depends on your situation.

Upgrade in place preserves your installed applications, user accounts, and configuration. It is faster and requires less manual reconfiguration. The downside is that you may carry over “cruft” – old libraries, unused packages, and configuration quirks – that could cause subtle problems.

Fresh install gives you a clean, minimal system with the latest defaults. It is more work because you have to reinstall all your applications and restore your data from backup. But it can eliminate long-standing issues and is often recommended if your system is several releases old or if you have made many custom changes.

For most users with a well-maintained Debian 11 system, an in-place upgrade is perfectly safe. If you are running a server with complex services, a fresh install might be safer if you have the time to set it up.

Costs and Risks

Debian is free software, and the upgrade itself costs nothing. However, you should consider the “costs” in terms of time and risk:

Time: The upgrade can take anywhere from 30 minutes to several hours depending on your internet speed and the number of packages.
Risk: There is always a small chance of breakage, especially if you use third-party repositories or have heavily customized your system.
Compatibility: Some older hardware may not be fully supported by the newer kernel, though Debian 12 still supports a wide range of architectures.

To mitigate risks, do the upgrade when you have time to troubleshoot, not right before a deadline.

Alternatives to Upgrading

If you are not ready to upgrade to Debian 12, you have a few alternatives:

Stay on Debian 11: Bullseye is supported until at least 2026 (LTS support). You will continue to receive security updates, but you will miss new features.
Use Debian 12 on a separate partition or virtual machine: This lets you test the new release without affecting your current system.
Switch to a different Debian-based distribution (like Ubuntu or Linux Mint) that uses newer packages, but that is a bigger change.

For most users, upgrading to Debian 12 is the recommended path because it gives you long-term support (until 2028) and access to newer software.

Frequently Asked Questions

Will my custom repositories break after upgrading? Possibly. Third-party repositories that are not updated for Bookworm may cause dependency conflicts. Before upgrading, disable or remove any non-Debian repos, and re-enable them only after the upgrade if they support Bookworm.

Can I skip a release and upgrade from Debian 10 to 12? No, the official upgrade path is only from the previous release (11 to 12). To go from 10 to 12, you must first upgrade to 11, then to 12. Skipping releases is not supported and can seriously break your system.

What if the upgrade fails halfway? If apt fails, do not reboot immediately. Run sudo apt --fix-broken install and then sudo apt full-upgrade again. If you have already rebooted and the system does not boot, use a live USB to chroot and fix the package manager manually.

Do I need to reinstall my desktop environment? No, the upgrade will automatically replace your desktop packages with the Bookworm versions. However, you may want to log out and back in after the upgrade to ensure all components are using the new versions.

Is it safe to upgrade a production server? It can be, but you should test the upgrade on a staging server first. Servers with custom kernels, proprietary drivers, or complex network configurations are more likely to encounter issues. Always have a rollback plan, such as a full disk image.

How long does Debian 12 receive support? Debian 12 will be supported for about 5 years, until June 2028. After that, you will need to upgrade to Debian 13 (Trixie) to continue receiving security updates.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →