How To Enable Backports And Testing Repositories In Debian 13 Trixie

Debian 13 “Trixie” shipped just recently—on August 9, 2025—bringing major updates like Debian Plasma 6 and RISC-V architecture support (Wikipedia). With that fresh start, many users want access to newer software, and that’s where backports and testing repositories come in. Here’s how to enable both, safely and cleanly.

What Are Backports and Testing Repositories?

• Backports are packages taken from Testing (currently “Forky”) and rebuilt to run on Stable. It gives you newer software without compromising system reliability.
• Testing is the next release in the pipeline—less tested than Stable but newer than backports. Use it with caution and preferably on a per-package basis.

Debian 13’s deb822 .sources Format

Debian 13 replaces the old /etc/apt/sources.list with per-repository .sources files in /etc/apt/sources.list.d/, using a modern key-value (deb822) layout. This is more readable, modular, and secure.

Step 1: Enable Backports

1. Create a file:
   sudo nano /etc/apt/sources.list.d/debian-backports.sources
2. Add:
   Types: deb deb-src
URIs: http://deb.debian.org/debian
Suites: trixie-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Enabled: yes
3. Save and run:
   sudo apt update
   You’ll now see trixie-backports listed—but note, it’s low priority by default, meaning you must explicitly install from it.
4. To install from it:
   sudo apt install -t trixie-backports <package-name>

Step 2: Enable Testing (Forky)

1. Create a file:
   sudo nano /etc/apt/sources.list.d/debian-testing.sources
2. Use the specific codename (recommended):
   
   Types: deb deb-src
URIs: http://deb.debian.org/debian
Suites: forky
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Enabled: no
   
   Avoid using testing as alias—it may auto-switch to a newer branch when Trixie is replaced.
3. Update your repo list as needed:
   sudo apt update
4. When necessary, install from testing:
   sudo apt install -t forky <package-name>

Best Practices & Tips

• Backports are safer; they’re rebuilt for stable.
• Testing is riskier—can introduce instability or dependency mismatches.
• Always use -t to explicitly install from non-stable repos.
• Configure aliases for convenience:
  alias apt-backports='sudo apt install -t trixie-backports'
alias apt-testing='sudo apt install -t forky'
• Use apt policy <package> to verify package source. When unsure, run simulated installs with -s and check pinning.

Quick FAQ

• Why use codenames like forky instead of testing?
  To prevent unintended upgrades when the testing branch changes.
• Are backports available immediately?
  Often not. They may be empty right after release and get populated gradually as maintainers rebuild packages.
• How to disable repositories?
  Either rename the file (e.g., add .disabled) or delete it—and follow up with sudo apt update.

Final Thoughts

Backports let you stay on stable while still grabbing newer packages—perfect for users who need that one latest tool. Testing opens the door to even newer versions, but tread carefully. With the new deb822 format, Debian makes managing these sources cleaner and safer. Use backports where possible, and reserve testing for targeted, informed use.

Mark Vincent

Tech enthusiast and content creator passionate about making technology simple for everyone. I share practical tips, guides, and reviews on the latest in computers, software, and gadgets. Let’s explore the digital world together!