Debian 13 trixie includes numerous updated software packages

Debian 13 trixie released
August 9th, 2025

After 2 years, 1 month, and 30 days of development, the Debian project is proud to present its new stable version 13 (code name trixie).
trixie will be supported for the next 5 years thanks to the combined work of the Debian Security team and the Debian Long Term Support team.
Debian 13 trixie ships with several desktop environments, such as:

• GNOME 48,
• KDE Plasma 6.3,
• LXDE 13,
• LXQt 2.1.0,
• Xfce 4.20
  This release contains over 14,100 new packages for a total count of 69,830 packages, while over 8,840 packages have been removed as obsolete. 44,326 packages were updated in this release. The overall disk usage for trixie is 403,854,660 kB (403 GB), and is made up of 1,463,291,186 lines of code.

Thanks to our translators who have made the man-pages for trixie available in multiple languages.

The manpages-l10n project has contributed many improved and new translations for manual pages. Especially Romanian and Polish translations are greatly enhanced since bookworm. All architectures other than i386 now use a 64-bit time_t ABI, supporting dates beyond 2038. Debian contributors have made significant progress towards ensuring package builds produce byte-for-byte reproducible results. You can check the status for packages installed on your system using the new package debian-repro-status, or visit reproduce.debian.net for Debian's overall statistics for trixie and newer.
Debian 13 trixie includes numerous updated software packages (over 63% of all packages from the previous release), such as:

• Apache 2.4.64
• Bash 5.2.37
• BIND DNS Server 9.20
• Cryptsetup 2.7
• curl/libcurl 8.14.1
• Emacs 30.1
• Exim (default email server) 4.98
• GNUcash 5.10
• GNU Compiler Collection 14.2
• GIMP 3.0.4
• GnuPG 2.4.7
• Inkscape 1.4
• the GNU C Library 2.41
• LibreOffice 25.2
• Linux kernel 6.12 LTS series
• LLVM/Clang toolchain 19 (default), 17 and 18 available
• MariaDB 11.8
• Nginx 1.26
• OpenJDK 21
• OpenLDAP 2.6.10
• OpenSSH 10.0p1
• OpenSSL 3.5
• Perl 5.40
• PHP 8.4
• Postfix 3.10
• PostgreSQL 17
• Python 3, 3.13
• Rustc 1.85
• Samba 4.22
• Systemd 257
• Vim 9.1

With this broad selection of packages and its traditional wide architecture support, Debian once again stays true to its goal of being The Universal Operating System. It is suitable for many different use cases: from desktop systems to netbooks; from development servers to cluster systems; and for database, web, and storage servers. At the same time, additional quality assurance efforts like automatic installation and upgrade tests for all packages in Debian's archive ensure that trixie fulfills the high expectations that users have of a stable Debian release.

This release for the first time officially supports the riscv64 architecture, allowing users to run Debian on 64-bit RISC-V hardware and benefit from all Debian 13 features. A total of seven architectures are officially supported for trixie:

• 64-bit PC (amd64),
• 64-bit ARM (arm64),
• ARM EABI (armel),
• ARMv7 (EABI hard-float ABI, armhf),
• 64-bit little-endian PowerPC (ppc64el),
• 64-bit little-endian RISC-V (riscv64),
• IBM System z (s390x)

i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware.

trixie will be the last release for the armel architecture. See 5.1.3. Last release for armel in the release notes for more information on our ARM EABI support.

The Debian Cloud team publishes trixie for several cloud computing services:

• Amazon EC2 (amd64 and arm64),
• Microsoft Azure (amd64),
• OpenStack (generic) (amd64, arm64, ppc64el),
• PlainVM (amd64, arm64, ppc64el),
• GenericCloud (arm64, amd64),
• NoCloud (amd64, arm64, ppc64el)

The genericcloud image should be able to run in any virtualised environment, and there is also a nocloud image which is useful for testing the build process.

Cloud images provide automation hooks via ``cloud-init`` and prioritize fast instance startup using specifically optimized kernel packages and grub configurations.