Salsa CI requires "debian/include/binaries" when adding/changing tests
Starting with commit 27b730ec "Don't just run the tests but build the Debian package instead using Salsa", Continuous Integration starts by building a debian package.
As observed when
gbp buildpackage -uc -us --git-debian-branch=yourbranch fails, recent
strip-determinism commits - especially commits submitted to the CI - are packaged as debian patches separately from the "upstream" tarball. See https://www.debian.org/doc/manuals/maint-guide/dother.en.html#patches for more background. In this case "upstream" seems to be the latest strip-nondeterminism release as explained in
Now any naive attempt to add or change any binary file (typically: some test asset) causes this type of failure: https://salsa.debian.org/reproducible-builds/strip-nondeterminism/pipelines/59941/failures
dpkg-source: error: add t/fixtures/jmod/test1.jmod.in in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to t/fixtures/jmod/test1.jmod.out: binary file contents changed dpkg-source: error: add t/fixtures/jmod/test1.jmod.out in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i -I -b . subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -i -I failed gbp:error: 'debuild -i -I -uc -us' failed: it exited with 29 ERROR: Job failed: exit code 1