[SOLVED] Inconsistency in sources after distribution upgrade to Trixie

Support
1

Background

The “Distribution Update” failed to update from Bookworm to Trixie. I also noticed several errors in the logs (e.g., “Unable to correct problems, you have held broken packages”).

To resolve these issues I did a manual update following the wiki page “FreedomBox Manual Upgrades” and the Discourse topic “Issue with Distribution Update page on Pioneer FreedomBox”.

It appears to have worked and FreedomBox > System > Upgrades now says “You are running Debian GNU/Linux 13 (trixie) and FreedomBox version 25.9.3.”

Issue

I took a look at /etc/apt/sources.list and /etc/apt/sources.list.d/freedombox2.list and I see an inconsistency.

sources.list refers to stable (i.e., Trixie):

$ less /etc/apt/sources.list

deb tor+http://deb.debian.org/debian stable main
deb-src tor+http://deb.debian.org/debian stable main

deb tor+http://deb.debian.org/debian stable-updates main
deb-src tor+http://deb.debian.org/debian stable-updates main

deb tor+http://security.debian.org/debian-security/ stable-security main
deb-src tor+http://security.debian.org/debian-security/ stable-secu

sources.list.d/freedombox2.list refers to bookworm-backports:

$ less /etc/apt/sources.list.d/freedombox2.list 
# This file is managed by FreedomBox, do not edit.
# Allow carefully selected updates to 'freedombox' from backports.

deb tor+http://deb.debian.org/debian bookworm-backports main
deb-src tor+http://deb.debian.org/debian bookworm-backports main

Questions

How do I resolve this? Can one ignore the warning that the freedombox2.list should not be edited and change bookworm-backports to trixie-backports?

Thank you for your help!

2

Instead of ‘stable’ it should refer to ‘trixie’ everywhere. Earlier Pioneer images were shipped this way but since then we only use codename instead of ‘stable’. This helps in explicitly controlling distribution upgrade process.

Yes you may. You can also re-run setup for Updates app to make this happen automatically. It does happen automatically in a day or so after the distribution upgrade, so you can just let it be. We should have included this step in the distribution upgrade process.

1 Like