Today update of APT up to 2.9.26 provided a new format of sources list on Trixie.
The default Debian Trixie repository list is located at:
/etc/apt/sources.list.d/debian.sources
as follows:
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: trixie-security/updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Debian Trixie multimedia list:
/etc/apt/sources.list.d/unofficial-multimedia-packages.sources
as follows:
Types: deb
URIs: http://deb-multimedia.org/
Suites: trixie
Components: main non-free
Signed-By: /etc/apt/trusted.gpg.d/deb-multimedia-keyring.asc
Sparky Sisters list:
/etc/apt/sources.list.d/sparky.sources
as follows:
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: core
Components: main
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: sisters
Components: main
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
The transition is made automatically during the APT package upgrade.
Indeed not automagically complete.
Manually creating debian.sources and renaming sources.list does indeed work for the new DEB822 but there are issues with this and until sorted, probably not be enforced.
For 1, synaptic does not recognise the new repo setup.
It didn’t work for me unfortunately. After installing SparkyLinux on my laptop with a brand new Kingston 480GB SSD, which ran fine in the first minutes, gave me an unbootable system right after updating the system for the first time. Recovering the system was a no-go, because even in the recovering mode I got error after error. The text was so long and went so fast through the screen, I just couldn’t read what it said. So no, I can’t tell you where it went wrong.