Dear web team,

If you compare the tracker page to madison results for packages listed
[1] in the 13.3 stable point release, it's apparent that only madison
has the current versions listed.

I am not sure how tracker works on the backend, but maybe some sync task
got stuck?

For example:

https://tracker.debian.org/linux-signed-amd64

 >  stable: 6.12.57+1

https://qa.debian.org/cgi-bin/madison.cgi?package=linux-signed-amd64&table=debian&a=&c=&s=#

 >  linux-signed-amd64 | 6.12.63+1         | trixie             | source


I didn't check every single package on the list but picked a few at
random and confirmed that the issue is also present with at least:
base-files, dhcpcd, apache2 and qemu.

Thanks for your work,

sney

[1] https://www.debian.org/News/2026/20260110

Hi,

I don't know exactly what happened, but yes I had to force re-run the
"update_repositories" task:
hertzog@ticharich:/srv/tracker.debian.org/distro-tracker$ sudo -u qa flock -n ../data/pids/run_all_tasks.lock ./manage.py tracker_update_repositories --force-update

It's now fixed.

Looking at the logs, I don't see any trace of the stable repositories
having been scanned/updated since the release. That somehow hints at the
fact that the code in distro-tracker/core/retrieve_data.py in
UpdateRepositoriesTask.execute_main() doesn't work as expected:

        updated_sources, updated_packages = (
            self.apt_cache.update_repositories(self.force_update)
        )

That should return the list of Packages and Sources files that have
had changes since the last run. This is actually managed in
the AptCache.update_repositories() method in
distro_tracker/core/utils/packages.py.

Cheers,