Stefano Zacchiroli <[EMAIL PROTECTED]> writes: > On Sun, Dec 30, 2007 at 10:10:35AM -0800, Russ Allbery wrote: >> Note that you can tell whether a package has lintian warnings or errors >> based on the contents of <http://lintian.debian.org/reports/qa-list.txt>. >> If it has no errors or warnings, it won't be listed.
> Cool, I wasn't aware of that. So this is the way to go for the PTS: > download daily the list of packages with errors/warnings, and generate > links only for them. This is a general recipe followed also per other > kind of links, e.g. svnbuildstat (now that it is fixed). You could also use the contents of this file to show the number of errors and warnings on the PTS page of the package. >> However, be aware that the next version of lintian will offer two >> lintian pages for each maintainer, one view that shows only errors and >> warnings as is currently done and a second that offers a full view that >> includes info, experimental, and overridden tags. The PTS may >> eventually want to link to both. > No problem, what do you suggest for the policy for presenting links from > the PTS? i.e. when do you want to see the link to one and when the link > to the other? I think it would make the most sense to show links to both pages if they both have contents, or to show a link only to the full page if there are no warnings or errors. You'd want to distinguish between the two links somehow to make it clear that one is only warnings and errors (and generally what people have to worry about), and the other shows the full report including things that aren't necessarily problems. >> I'm not sure if I should leave qa-list.txt as-is and generate a second >> full list with more columns, or add more columns to the existing file. >> Probably the former to be safe. > PTS side there wouldn't be any significant difference, since the > conditional logics for presenting lintian links is not yet implemented. > Hence I'm for the simpler solution: one single file with all the info. Well, I'm sure *someone* is using qa-list.txt, since it was added originally by request, but it's not the PTS. I'm not sure what it is. The cross-archive report that highlights packages that haven't been uploaded in a while that was running from someone's people.d.o page (I forget who or where) uses it, I think. I just don't want to break anyone else's software. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]