On Fri, 2017-04-28 at 19:02 +0200, Orestis Ioannou wrote: > Doing so would enable us to actually know which packages do have > patches, or better which versions of each package have patches. I need an API that can help make these links more like the 4th link by exporting the amount of patches for each supported package version: https://packages.qa.debian.org/~pabs/g/glibc.html (want patch counts, versions/suites in title attributes) https://packages.qa.debian.org/~pabs/n/nsis.html (3.0 has no patches, needs hiding) https://packages.qa.debian.org/~pabs/0/0xffff.html (no version has patches, all need hiding, want single version anyway) https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=779400;filename=distro-tracker-patches-mockup.png;msg=5 For me the ideal data set would be a list of packages with 1 or more patches, each with the associated suite names, version numbers and patch counts, or files patched counts for packages that use diff.gz. I'd prefer if it didn't include patch info for obsolete suites. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part