On 03/12/2025 14:21, Alexander V. Makartsev wrote:
On 03.12.2025 07:29, Max Nikulin wrote:
On 03/12/2025 01:39, Alexander V. Makartsev wrote:
$ apt policy
Package files:
...
I have not spotted anything unusual.
Somehow "trixie-proposed-updates" gets priority 500 which is wrong and
it should be treated like "trixie-backports" with lower priority.
I don't see the difference between them, if there is no guarantee that
packages will not vanish from there.
Did they really vanish?
$ apt policy curl
8.14.1-2 500
500 https://deb.debian.org/debian trixie/main amd64 Packages
But 8.14.1-2+deb13u2 is currently in
http://deb.debian.org/debian trixie/main amd64 Packages
So I still suspect either stale mirror or update during interval between
sync of proposed-updates and main trixie section.
I will pin everything from "trixie-proposed-updates" to lower priority,
so packages from this source won't be considered as candidates.
And wait long enough to get candidate versions from "stable-updates".
Probably it is good idea to report somewhere about this issue, so it
gets a proper fix.
A note on possible interference of backports and proposed updates may be
added to <https://wiki.debian.org/StableProposedUpdates> and linked from
<https://wiki.debian.org/Backports>. Either I missed something or what
you faced should not be a frequent accident. Perhaps there is a more
plausible chance to get unsolicited packages from backports if
proposed-updates are disabled after single upgrade from proposed
updates. Pinning of upgraded packages may be required. Removing of
packages from proposed-updates without their migration either to updates
or to stable sounds like something exceptional. Your list is rather long.
