TLDR: I have plans to get fresh archive-wide data about lintian results in UDD (and then to any service that wants to consume it), but it's still WIP
Hi, Seeing that lintian got adopted, I got motivated into looking if I could help on the lintian.d.o side, that is, provide up-to-date archive-wide up to date to developers. Since the architecture of lintian.d.o seemed quite complicated, I instead decided to follow what worked for other UDD-based data importers (such as the one that scans for new upstream versions). So my plan is the following: - use a UDD postgresql table for data storage - use UDD to decide which packages need to be analyzed - coordinate the analysis from UDD, but do the analysis itself on a third-party 'worker' machine (since the process is quite CPU intensive) - provide visualisation directly on https://udd.debian.org (similar to https://udd.debian.org/dmd/ or https://udd.debian.org/bugs/) - work with data consumers on how to best export the data from UDD to them I know it feels a bit like NIH, but I believe the simpler design will help in the long term... The current status is: - there's now a lintian_results table in UDD - there's a new lintian importer that coordinates the analysis - the lintian_results is currently being populated (~6400 source packages processed at the moment, ~29000 remaining -- I expect the initial analysis to be over in about 3 days) What remains to be done: - bugfixing? - work on the visualisation part. There was a UDD CGI that did this using the old data (from lintian.debian.org) at https://udd.debian.org/lintian/ that could serve as a basis - talk to DSA about migrating the "worker" VM to Debian infra (it's just a dumb VM, so it should not be an issue) - talk to lintian data consumers - see what we want to do about lintian.d.o Lucas
