Hi Lucas, TL;DR please find one idea to solve your issue below
> provide the current > status of the archive against the current version of lintian as > something parsable Just for lintian.d.n (which is about to be transferred to lintian.d.o), that is exactly what we provide. It just won't be one file like it used to be. We plan instead to produce packaging hints based on heuristics designed to provide the best service to *maintainers*. I am sorry about the inconvenience, but as a service facing the public—a distinction you likewise recognized in your previous message—the change makes sense for us. We hope to prioritize based on: - packages for which no or no recent runs are available - frequency of uploads (more uploads, better data) - team requirements (for their statistics) UDD can subscribe to the AQMP "results" queue and decide independently, i.e. based on other input, when "a run across the archive" is substantially complete. We previously used DAKweb for that purpose, but our services are now available in real time. But why wait? Why not just add a "lintian_version" column to your table [1] and update the table at regular intervals, when you have collected a sufficient number of runs? The Lintian version is in our JSON results. Next, cut from your table those sources no longer known to the archive. For an example of how to do that, please see here for a solution via DAKweb. [2] That is the script we use now to DROP, via ON CASCADE DELETE, website data that is obsolete due changes in the archive. HTH Kind regards Felix Lechner [1] https://udd.debian.org/schema/udd.html#public.table.lintian [2] https://salsa.debian.org/lintian/taxiv/-/blob/master/get-archive-state#L149-150