The build path is embedded in /usr/bin/rotter:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/rotter.html

  /build/1st/rotter-0.9/src/rotter.c:478
  vs.
  /build/2/rotter-0.9/2nd/src/rotter.c:478

The attached patch to debian/rules fixes this by adding a
dh_auto_configure override which passes the default CFLAGS provided by
dpkg-buildflags.

Alternately, updating to a newer debhelper compat level might also solve
this issue as well as other issues.

With this patch applied rotter should build reproducibly on
tests.reproducible-builds.org!

Thanks for maintaining rotter!

live well,
  vagrant

Dear Maintainer,

Because Debian builds packages from a fixed build path, neither the 'reprotest'
utility in Salsa-CI, nor the Reproducible Builds team's package test
infrastructure for Debian[1] currently check for equivalent binary package
output from differing source package build paths.

This means that your package will pass current reproducibility tests; however
we believe that source code and/or build steps still embed the build path into
the binary package output, making it more difficult than necessary for
independent consumers to check the integrity of those packages by rebuilding
them themselves.

As a result, this bugreport will remain open and be re-assigned the 'wishlist'
severity[2].

For more information about build paths and how they can affect reproducibility,
please refer to: https://reproducible-builds.org/docs/build-path/

Thanks,
James

[1] - https://tests.reproducible-builds.org/debian/reproducible.html

[2] - https://www.debian.org/Bugs/Developer#severities

A correction for a mistake in my previous message:

Currently the 'reprotest' job in Salsa-CI does in fact continue to exercise
variations of the build-path, and will fail if it builds binary packages that
contain different contents as a result.