[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1109680: marked as done (release.debian.org: use lintian results to block testing migration)

Your message dated Sat, 23 Aug 2025 10:47:12 +0200
with message-id <8fbdc433-102b-47c9-b3e4-919cd733e938@debian.org>
and subject line Re: Bug#1109680: release.debian.org: use lintian results to block testing migration
has caused the Debian Bug report #1109680,
regarding release.debian.org: use lintian results to block testing migration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1109680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109680
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Hi,

On 21-07-2025 22:26, Lucas Nussbaum wrote:

Let me know if that works for you.
This now is active, seehttps://qa.debian.org/excuses.php?package=gitlab-ci-multi-runner 

Thanks for your work on this and the idea.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: