Bug#797096: Distro Tracker should rely on "codename" and not "suite" to update its view of repositories
Package: tracker.debian.org
Tags: newcomer
Only the "codename" of a repository is guaranteed to not be modified during
the life of the repository. The "suite" is usually just an alias that
might point to different repositories over time (it's a symlink in the
archive).
And when the "suite" field (of Repository object) in distro-tracker is out
of sync with the symlinks on the mirrors, you start importing data in the
wrong repository.
This is not a big problem for Debian currently because we don't display
codenames and don't generate news about changes in the repositories (we
only import such news from incoming email)... but I had the problem in
Kali where the tracker claims that a package is in a given release when
in fact it never was:
http://pkg.kali.org/pkg/backports.ssl-match-hostname
=> this one was never in moto, but when kali-current switched to point
to sana, it claimed that it was added to moto...
Thus we must update all the code in distro_tracker/core/models.py
and distro_tracker/core/retrieve_data.py and the associated tests
to make sure that we rely on the codename when updating distro-tracker's
view of the various repositories.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Reply to: