Good to know. I’m thinking of changing my laptop - which I usually only use when travelling - to Debian just so I don’t have to remember to keep it up to date.
MIPS64 is dropped as a supporting architecture. Very soon SPARC and PowerPC architectures will be dropped along with 32-bit x86 architecture too.
Only grouse for Debian, unlike Arch they do not provide support for all the Linux LTS Kernels.
A Debian needs to be updated as well.
Keep it up to date, they do not provide updates to their packages for nothing.
I’m very excited. I’ve had a debian computer since Jan 2024, and it’s been really great. I’m excited for the update, but if not, things have also just been great. It’s a strange feeling being ok with it as it is.
I couldn’t wait, so I went into my apt sources list and changed my bookworm tags to trixie followed by a sudo apt update && sudo apt full-upgrade.
At this stage of trixie’s testing branch, it’s extremely stable and since the hard freeze is official, it will only get more and more better from here.
The good thing about debian is that you can keep a system stable for 5 years. No changes in the APIs during that time. I love it. My home server is running debian bookworm with portainer and a couple of docker containers. It gets support until 2028. I will eventually start looking into debian trixie in 2026 
If you use Debian strictly as a server, have a gander at DietPi which is a minimal headless Debian fully configured and optimized for self-hosting.
This is not for me. I only use orginal debian stable. This is basically a matter of trust. Over 20+ years of experience with debian I have ultimate trust in debian stable. This can not be enhanced by moving to another distro.
There are some devices such as Raspberry Pi’s, hence the name DietPi, where OG Debian is not the practical choice in terms of performance.
That’s where DietPi shines and that’s why it exists. After all, necessity is the mother of all creation.
If it’s not for you, it’s not for you.
So, if you just change to trixie now, and then when it turns to “stable” are you just staying on stable? Or does it move into the next version of “testing”? I’ve never tried before.
Since your repos in the sources.list should be for Trixie, you will switch from testing to stable branch and the current stable, Bookworm will become oldstable branch.
Debian offers flexibility in how you configure your sources list, using either codenames like bookworm or trixie, or branch names like stable or testing. If you change your sources list from bookworm to trixie, you’ll switch to the testing branch, which is currently Trixie. When Trixie becomes the stable release, your system will remain on Trixie without needing to modify the sources list again, as it will automatically be the stable version.
Alternatively, if your sources list uses stable instead of a codename, your system will automatically transition from bookworm to trixie when trixie becomes the new stable release, without requiring any changes. The choice depends on your preference. If you want to always stay on the stable branch, use stable in your sources list. If you want to switch to trixie now and continue using it when it becomes stable, set your sources list to trixie. You can keep trixie as the codename or switch to stable later, and your system will still be on the stable release since trixie will have become stable. This system is designed to be straightforward yet powerful, giving you control over how you track Debian releases.
I read in Debian somewhere I didn’t want to use “stable” for some reason as it could have some unintended consequences during upgrade time. . . but I wasn’t sure why enitirely other than you don’t really purposely upgrade and don’t backup properly?? I guess it makes sense if I put in “trixie” though. I appreciate that is very thorough and I’m sure I could find this info somewhere. You rattled that off pretty easy though. Thanks for that a lot! I’m on the fence. I’ll probably just wait.
Seems they’ve changed source list from /etc/apt/sources.list to /etc/apt/sources.list.d/debian.sources with different format for Trixie.
For me on Debian12 /etc/apt/sources.list.d is an empty directory.
They deleted the old sources.list after the upgrade or still kept it?
You’re given the option to “modernize” the sources list on the first apt update after booting into trixie.
Hang on, that looks awesome. I just checked out that link and what a handy thing that distro looks like, I’m gonna check it out.
I followed the “modernized” option and my debian.sources looks like this:
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://www.nic.funet.fi/debian/
Suites: trixie
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://www.nic.funet.fi/debian/
Suites: trixie-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
So is that how it should look?
Yes, that’s the modernized sources.