On Mon, Nov 06, 2023 at 09:52:54PM +0100, Diederik de Haas wrote: > > And libx11-dev is only used in some tests. > > We can annotate libx11-dev <!nocheck>. > > Is that still the case?
I don't know. I filed the patch more than two years ago. A relatively > Can you perhaps expand on why that annotation is appropriate (for my learning > experience)? Policy 4.9.1 mentions "to not run any build-time test suite > provided by the package" with the 'nocheck' tag, but that sounds a bit heavy- > handed to me? The technical term for <!nocheck> is "restriction formula" according to man deb-src-control. It expresses that when the nocheck build profile is enabled, the annotated dependency is disabled. The nocheck build profile may be used together with the nocheck build option to disable running build-time tests. Any such testing is not supposed to affect the output artifacts of the package in case the build succeeds. The method I used for validation here is performing such a nocheck build and comparing its artifacts with a regular build using diffoscope. I am not sure what you mean with heavy-handed here and why that would be an issue. Note that none of the regular build daemons used for building packages on release architectures ever enable this build profile. It is enabled on some ports architectures and it is also enabled by default for cross builds. Nevertheless, a failure to build with a nocheck profile is considered release-critical since trixie, because the autoremover will consider breaking <!nocheck> annotated dependencies. Helmut
