On Wed, 16 Apr 2025 at 18:40:00 +0200, Paul Gevers wrote:
In one of the reports I read this:
"""
* When a package is built with the nocheck profile, it means:
- DEB_BUILD_OPTIONS=nocheck
(the tests should be skipped during the build)
- DEB_BUILD_PROFILES=nocheck
(Build-Depends marked <!nocheck> are not installed)
- The contents of the package is allowed to be different than normal
"""
I don't think that's true. I was very much under the impression that
with the build profile nocheck all binaries have to be build and the
content has to be the same.
The definition of the nocheck build profile on
https://wiki.debian.org/BuildProfileSpec agrees with Paul's impression.
I think it's reasonable for Santiago's mass-rebuild not to verify whether
those desired properties were actually true (to verify them, he would have
had to build the package twice, with and without nocheck, defeating the
purpose of wanting to skip potentially flaky or slow build-time tests)
but it would be better if future bug reporting for this scenario didn't
encourage maintainers to implement nocheck incorrectly.
So perhaps instead of
The contents of the package is allowed to be different than normal
the bug template should be more like
The contents of the resulting package are meant to be identical to
the package produced by a normal build, but this was not checked
during this particular mass-rebuild
or something along those lines?
smcv
