Notes for pgrouting - reproducible builds result

Version annotated: 2.2.4-1
Identified issues:
Identifier: gcc_captures_build_path
Description Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd
Currently we vary the build path only when testing packages from unstable
and experimental, for testing and stable we recommend that rebuilds
are done in the same path as the original build.
.
dpkg-buildflags version 1.20.6+ sets -ffile-prefix-map by default
(and -fdebug-prefix-map in older versions) which fixes this issue
in many cases, but not all (see: records_build_flags).
.
There are patches submitted upstream to address this specific issue, but they
are unlikely to be merged at this point:
.
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html
.
When this is accepted into GCC upstream, we could remove this note.
In the meantime, please do not remove this issue, nor mark it as deterministic,
nor untag these packages.
Identifier: captures_kernel_version_via_CMAKE_SYSTEM
Description Uses CMAKE_SYSTEM, which embeds `uname -sr` output; the -r (version) varies.
.
Instead, use CMAKE_SYSTEM_NAME (`uname -s`), which shouldn't vary.
.
May also be triggered by use of CMAKE_HOST_SYSTEM,
CMAKE_HOST_SYSTEM_VERSION or CMAKE_SYSTEM_VERSION.
.
Parent issue: captures_kernel_version
Identifier: timestamps_in_cmake
Description Timestamps generated by cmake TIMESTAMP function respect
SOURCE_DATE_EPOCH, but use the local timezone. In CMakeLists.txt,
uses of the TIMESTAMP function need to specify the timezone as
UTC:
.
string(TIMESTAMP CURRENT_TIME "%Y-%m-%d" UTC)
.
Likely affected packages:
https://codesearch.debian.net/search?q=string%5C%28TIMESTAMP.*%5B%5EU%5D%5B%5ET%5D%5B%5EC%5D%5C%29&literal=0
 

Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).