Bug#1126450: tracker.debian.org: Package versions not updated for 13.3 point release
Raphael Hertzog <[email protected]> Tue, 3 Feb 2026 14:39:11 +0100
| Newsgroups | gmane.linux.debian.devel.quality-assurance |
|---|---|
| Message-ID | <aYH6f9g4Azkx3NU6__1889.36272622726$1770126098$gmane$org@fr13-buxy.home.ouaza.com> |
Hi,
On Mon, 26 Jan 2026, Jesse Rhodes wrote:
> 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?
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,