Bug#786644: reproducible builds should vary whether nocheck is added to DEB_BUILD_OPTIONS
Hi Helmut,
> I'd expect that setting DEB_BUILD_OPTIONS=nocheck on a package build
> should not change the resulting binary packages. It might make the build
> succeed despite being broken, but if it succeeds without nocheck, it
> should be no different when enabled.
Policy is, however, silent on whether that is the correct behaviour or not.
Clarifying policy as to what the correct behaviour should be seems to be a
necessary first step. I would expect that policy would end up saying something
"should" (and not "must") happen with nocheck; I'm not sure that checking non-
mandatory things is sensible in this context.
That said, the policy editors are often interested in seeing scope of the
impact of any change and the only way of knowing how many packages would be
made instabuggy by this change is to include it in the tests...
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Reply to: