Hi, maybe one should make that "every build" to not confuse it with "all"?
Regards René Am 26. Februar 2026 12:05:05 MEZ schrieb Paul Gevers <[email protected]>: >Hi Lucas, > >On 2/26/26 10:41, Lucas Nussbaum wrote: >> On 23/02/26 at 20:57 +0100, Paul Gevers wrote: >>> Somehow it seems we got data from udd that confused britney2 to follow the >>> code path to report that lintian crashed instead of waiting for data (which >>> means that there were "lintian failed" results for the not-yet-built >>> version). Do you have any idea what happened? > > >Sorry. While I still think that the text "Lintian crashed and produced no >output, please contact debian-release for a hint" should only be presented if >the udd output has "lintian failed" for that package/version combination [2], >I also realized that it shouldn't even have gone through the udd code path >[3]. Looking at the excuses quoted by Rene none of the release architectures >were built yet, so the wording should have been "Lintian check deferred: >missing all builds". I think I just created a reproducer, so I'll probably be >able to fix this issue shortly. > >Paul > >[1] >https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/lintian.py?ref_type=heads#L106 >[2] >https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/lintian.py?ref_type=heads#L186 >[3] >https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/lintian.py?ref_type=heads#L78
