Debian backport repo priority issue

[rm-td]

Hello, Debian 13 hosts and client, version release 4.0.18-1 has been stable for ages, minor issue surfaced with new publication in backports. Not sure this should be flagged as required unless the specific package is deployed.

Client repo from patchman-client -d follows where we see default priority suggesting the above shouldn't occur.

Grateful for thoughts, thank you for patchman

repo tmp file

'deb' 'Debian 13 x86_64 repo at https://packages.wazuh.com/4.x/apt/dists/stable/main/binary-amd64' '500' 'https://packages.wazuh.com/4.x/apt/dists/stable/main/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://repo.openbytes.ie/patchman/debian/dists/trixie/main/binary-amd64' '500' 'https://repo.openbytes.ie/patchman/debian/dists/trixie/main/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://deb.debian.org/debian/dists/trixie-backports/main/binary-amd64' '100' 'https://deb.debian.org/debian/dists/trixie-backports/main/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://deb.debian.org/debian/dists/trixie-updates/main/binary-amd64' '500' 'https://deb.debian.org/debian/dists/trixie-updates/main/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://security.debian.org/debian-security/dists/trixie-security/non-free-firmware/binary-amd64' '500' 'https://security.debian.org/debian-security/dists/trixie-security/non-free-firmware/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://security.debian.org/debian-security/dists/trixie-security/main/binary-amd64' '500' 'https://security.debian.org/debian-security/dists/trixie-security/main/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://deb.debian.org/debian/dists/trixie/non-free-firmware/binary-amd64' '500' 'https://deb.debian.org/debian/dists/trixie/non-free-firmware/binary-amd64'
'deb' 'Debian 13 x86_64 repo at https://deb.debian.org/debian/dists/trixie/main/binary-amd64' '500' 'https://deb.debian.org/debian/dists/trixie/main/binary-amd64'

[furlongm]

What type of repos are in use? Host repos only?

[rm-td]

Hello, sorry for reply delay when you'd taken the time to ask. This could be a simple timing issue,

To answer - yes- host repos only.

However - its disappeared from affected VMs now. Given this was observed a few days ago there would have been meta refreshes and client checkins (daily cron job) so its corrected itself.
Curious it arose but unfortunately unless this backports issue happens again I am not sure its worth any effort to investigate. There is no value in taking up your time on a transient issue, feel free to close.
Thank you for patchman, it does what it says on the tin!

EDIT: I think I have found it - due to debian point release from 13.3 to 13.4 I am leaning towards patchman server knowledge being either in front of or behind any affected client. Having done at least an "apt update" on clients followed by patchman-client and a patchman -a session on the server all anomalies gone. Timing.

[furlongm]

Eventually consistent, I guess. Another reason this could have happened was OS repos in use. That used a different upgrade path, but I merged both in #800 so behaviour should be the same now. Closing this, feel free to reopen if the issue recurrs.