Bug#1109680: release.debian.org: use lintian results to block testing migration
Package: release.debian.org
Severity: normal
Hi,
I'm moving here the discussion that started on #debian-qa.
I wrote a CGI script¹ that exports lintian results per source package,
as YAML.
¹ https://salsa.debian.org/qa/udd/-/blob/master/web/cgi-bin/lintian-britney.cgi?ref_type=heads
http://udd.debian.org/cgi-bin/lintian-britney.cgi?tags=unstripped-binary-or-object,source-nmu-has-incorrect-version-number
The output looks like:
-------------------------------------------------->8
# package that has none of the tags listed
a2jmidid/9-3.1:
# architectures for which lintian was run
architectures: amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 s390x source
tags:
[...]
# package with one of the tags listed
a52dec/0.7.4-20:
architectures: amd64 arm64 armel armhf i386 mips64el ppc64el riscv64 s390x source
tags:
- source-nmu-has-incorrect-version-number
[...]
# package that failedGG
latex-cjk-chinese-arphic/2.2:
architectures:
status: lintian failed
-------------------------------------------------->8
The pseudo code to block packages would look like:
1. find stanza for source/version, if it cannot be found, we probably
want to wait until the package is processed.
2. if it contains 'status'='lintian failed', either block the package,
or ignore lintian alltogether
3. examine the architectures field. does it contain enough
architectures, compared to those we want to migrate? (we might not
want to wait for all architectures, but it's probably a good idea to
wait for a few ...)
4. examine the list of tags
The output could link to e.g. https://udd.debian.org/lintian/?a52dec
(The default display only lists errors and warnings, but I suppose we
are not going to block on anything else)
Let me know if that works for you.
I saw the discussion about the number of tag occurences for a given
source package, that should be used to identify regressions. Tags are
currently only listed once per source. It would be possible to add the
number of occurences for each tag (with distinct "information"). Let me
know.
Lucas
Reply to: