On 03/12/2025 01:39, Alexander V. Makartsev wrote:
It lists packages from "stable-backports" as upgrade candidates for
packages from "stable".
[...]
$ cat /etc/apt/sources.list.d/debian.sources
"apt policy" (*without* package name) might help to reveal other files
or preferences like improper Default-Release.
$ apt policy curl
curl:
Installed: 8.14.1-2+deb13u1
Candidate: 8.16.0-4~bpo13+1
Version table:
8.16.0-4~bpo13+1 100
100 https://deb.debian.org/debian trixie-backports/main amd64
Packages
*** 8.14.1-2+deb13u1 100
100 /var/lib/dpkg/status
8.14.1-2 500
500 https://deb.debian.org/debian trixie/main amd64 Packages
<https://tracker.debian.org/pkg/curl>
[2025-11-09] Accepted curl 8.14.1-2+deb13u2 (source) into
proposed-updates (Debian FTP Masters) (signed by: Samuel Henrique)
My guess is that "apt update" should cure the issue (unless your mirror
is stale).
Perhaps apt can not distinguish cases when some package version is
removed from backports and from proposed updates, so it just picks 100
(locally installed and missed in repositories) to 100 (backports) upgrade.
