Notes for darktable - reproducible builds result

Version annotated: 2.0.5-2
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: kodi_package_captures_build_path_in_source_filename_hash
URL https://salsa.debian.org/multimedia-team/kodi-media-center/kodi-audiodecoder-fluidsynth/-/commit/ec87abd2c45b6c18f36352c049dfdf425f3a0911
Description kodi-* packages sometimes have strange paths like SIDCodec.cpp.b78d5642 in
the binary (without the build path). The string suffix does not vary
between builds in the same build path, suggesting its a hash of the build
path.
.
Disabling Link-Time Optimization (LTO) and/or Debug Fission solves this
issue.
 

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).