|
Identifier:
|
gcc_captures_build_path
|
|
Description
|
Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd
.
Until early 2024 we varied the build path when testing packages from unstable
and experimental, which we have stopped doing now as the build path is recorded
as part of the environment and thus can be used when rebuilding.
.
This issue is kept here for the time being.
.
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:
|
randomness_in_documentation_generated_by_sphinx
|
|
URL
|
https://wiki.debian.org/ReproducibleBuilds/SphinxIssues
|
|
Description
|
Sphinx might output references to memory addresses and generate a json index file
with entries in random order or with non-deterministic values (eg. searchindex.js).
See https://bugs.debian.org/822197 for memory address issue
.
searchindex.js needs sort_keys=True (jsonimpl.py) but the key values vary too.
|