Debian 13 “Trixie” is anticipated to be released in the summer of 2025.
Is DietPi going to updated at the same time or later?
Thanks
Debian 13 “Trixie” is anticipated to be released in the summer of 2025.
Is DietPi going to updated at the same time or later?
Thanks
We will probably provide an update script to be able to change the Debian version. It will most likely be available around the release of Trixie. But it could also be a week or two later. The update has to be triggered by the user, similar to what we did with Bookworm. We don’t plan an automatic destro upgrade.
How would one trigger it, when it is ready?
THX
as reference Debian Bookworm has been released – DietPi Blog
THX.
I am currently have:
root@DietPi:~# echo “$G_DISTRO_NAME”
uname -a
“bookworm”
Linux DietPi 6.12.32+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.32-1~bpo12+1 (2025-06-21) x86_64 GNU/Linux
root@DietPi:~#
Would it be recommended to upgrade when released?
Depends on what your expectation from Debian Trixie is. It is certainly not wrong to wait a bit if there is no urgent reason.
THX. Than I will wait.
Can we consider your script as a stable → final (?), or should I wait a couple more days/weeks before there will be an official way to upgrade?
Pls stay with GitHub. It doesn’t make sense to post your question twice on different platforms
Hello, i also wanted to ask if there will be an official announcement how to upgrade to Trixie… Noticed the images for Raspberry still Bookworm; guess the next release is not ready yet.
The script is already ready for testing
For a production system it is recommend to wait for next DietPi release.
Thank you.
Well, Trixie is only a few days old. Personally, I would wait a little longer before upgrading, as long as it is not absolutely necessary. The question is always what you expect. Miracles won’t happen ![]()
I don’t know if this relevante for upgrade to Trixie when using DietPi.
I am using Roon myself but have not done any upgrade so far.
Torben
thx for sharing.
Reply from Roon support:
What likely happened here is that Debian upgrades often replace older versions of the libicu library with a newer one, and only install it if some system package explicitly requires it. For example, Debian 12 included libicu72, while Debian 13 provides libicu76. During the upgrade the old package is removed, but the new one may not be installed automatically if no default system component depends on it.
That’s why it looked like the package “disappeared” after the upgrade, and Roon couldn’t start until you manually installed the newer version.
Torben
Thanks for the heads-up. We handle this in our upgrade script already:
if apt-mark showmanual | grep -q '^libicu72$'
then
G_DIETPI-NOTIFY 2 'Migrating from libicu72 to libicu76'
G_AGI libicu76
G_EXEC apt-mark auto libicu72
fi
Though it only works if the old package is not somehow removed during the upgrade. This should not happen, did never during my tests, but I will check back with that user on the Roon forum.
Great THX
Torben