'Something went wrong' with APT sources.list - mixed release entries

[jrkb]

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.35
How are you able to access your server: The webadmin
SSH
Direct access via physical keyboard/screen
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: not that I’m aware

Describe your issue

I get error messages when using apt directly, and indirectly via yunohost tools up[date|grade]

I noticed that packages use mixed release entries. At times I see bookworm and at time stable.

yuno@host:~ $ cat /etc/apt/sources.list.d/yarn.list
deb [signed-by=/etc/apt/trusted.gpg.d/yarn.gpg] https://dl.yarnpkg.com/debian/ stable main
yuno@host:~$ cat /etc/apt/sources.list.d/extra_php_version.list
deb [signed-by=/etc/apt/trusted.gpg.d/extra_php_version.gpg] https://packages.sury.org/php/ bookworm main

Now that trixie is the new stable, isn’t that an issue? Is it safe (or even desired) to replace all stable entries in /etc/apt/sources.list.d/*.list with bookworm? Or should I rather use oldstable? I’m a bit afraid of shooting myself in the foot when updating.

Share relevant logs or error messages

yuno@host:~$ sudo yunohost tools update all
Info: Fetching available upgrades for system packages…
Warning: W: http://download.opensuse.org/repositories/devel:/languages:/crystal/Debian_12/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Error: Something went wrong while updating the cache of APT (Debian's package manager). Here is a dump of the sources.list lines, which might help identify problematic lines:
sources.list:deb http://ftp.debian.org/debian bookworm main contrib
sources.list:deb-src http://ftp.debian.org/debian bookworm main contrib
sources.list:deb [signed-by=/usr/share/keyrings/yunohost-bookworm.gpg] http://forge.yunohost.org/debian/ bookworm stable
sources.list:deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
sources.list:deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
sources.list:deb http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
sources.list:deb-src http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
sources.list.d/crystal.list:deb http://download.opensuse.org/repositories/devel:/languages:/crystal/Debian_12/ /
sources.list.d/yarn.list:deb [signed-by=/etc/apt/trusted.gpg.d/yarn.gpg] https://dl.yarnpkg.com/debian/ stable main
sources.list.d/extra_php_version.list:deb [signed-by=/etc/apt/trusted.gpg.d/extra_php_version.gpg] https://packages.sury.org/php/ bookworm main

[jrkb]

Okay, it still gave issues when I exchanged within source.list.d/yarn.list the stable keyword with either oldstable or bookworm.

So, I wondered what this yarn-repository was for. yarn wasn’t even installed. After checking what packages were installed from the yarn repository, it turned out that the repository was an orphan. No packages were installed from there. so I kicked it out.

While I was at it I got rid of the keyring deprecation warning. Now it seems all fine again, and I can update like normal. phew.

Btw, I assume that the repository got added when I installed some service - no idea which one. When I removed the service again, it must’ve stayed behind.