Le vendredi 9 août 2024, 12:08:29 UTC Lucas Nussbaum a écrit : > On 09/08/24 at 07:54 +0000, Bastien Roucariès wrote: > > Le vendredi 9 août 2024, 06:39:04 UTC Lucas Nussbaum a écrit : > > > On 08/08/24 at 18:40 +0000, Bastien Roucariès wrote: > > > > > > It is not meant to replace the corresponding UDD link, in fact I > > > > > > added a link to it in the page of each tag, to see all the affected > > > > > > packages. But I think it is better to first arrive on a very fast > > > > > > to load page that simply explains the tag, and then be able to > > > > > > follow a link to see the list of affected packages. > > > > > > > > What will be wonderfull is to retrieve number of package affected and > > > > do a svg graph along time... Using a static script > > > > > > Hi Bastien, > > > > > > Are you aware of https://trends.debian.net/ ? > > No but the same with every tag will be really really nice > > The raw data used by trends.d.n is not publicly available (mainly > because it's a bit too large). By if you are interested in specific > tags, I can probably look into extending trends.d.n to cover those tags.
Yes - source-is-missing - source-include* And all ftp reject tags > Note that trends.d.n works by running a given lintian version over all > packages (fetched from snapshot.d.o), not by running lintian on a > regular basis, because when lintian changes, the list of generated tags > also changes. We have here a mapping of renamed tag in a file in order to ease this kind of stuff. If you could put vertical bar every lintian version change, it will give clue about breaking series Bastien > > Lucas >
signature.asc
Description: This is a digitally signed message part.