buildd log scanner -- packages with tag W-build-stamp-in-binary -- Debian Quality Assurance

buildd log scanner tag `W-build-stamp-in-binary`

description

This tag means a build log has a line touching build-stamp or build-something-stamp when processing the binary-arch target.
This test has some false positives, most likely due to stdin/stderr ordering issues (many on hurd-i386, but also a larger number of armel and some on other architectures). Because of this it is ignored in the numbers exported to tracker.debian.org unless it shows up on at least 4 architectures.
build-stamp files are usually used as stamp files to make sure the upstream build process is only called once in the build target but not a second time in the binary target of debian/rules. As the build target is run as normal user, while the binary target is usually run under fakeroot, this ensures the package build is not tainted by any environment variables fakeroot might set. It also ensures compilation is only done once and not even some possible expensive up-to-date checking is done in the binary target.
Possible problems causing this warning:

build rule not depending on the (right) build-stamp file
'phony' build-stamp target:
A make rule is phony if it is listed in .PHONY, if it does not create a file named after the rule or if one of its prerequisites (recursively) is phony.
A common mistake is using a patch rule as prerequisite instead of its stamp file or using a config.status: configure rule for non-autoconf configure that is not generating a config.status file.
binary-arch depending (indirectly) on binary-indep-build: If e.g. the autobuilders call build-arch and your build-arch generates a build-arch-stamp file and your binary-arch (or a target being part of binary-arch, often called install) depends on build, which generates build-arch-stamp and build-indep-stamp then build-indep-stamp is only generated once binary-arch is called and this warning is triggered. (If your build-indep target is a no-op then this is not a problem yet, but better fix it now before you add something there and forget to fix this issue).
False positives:
sometimes the debian/rules binary-arch is found in the build log before output still originating from a previously executed command. This is usually limited to one or two, very seldom three architectures.

buildd log scanner tag W-build-stamp-in-binary

description

list of packages

buildd log scanner tag `W-build-stamp-in-binary`