| Version annotated: |
3.6.0-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:
|
random_hashes_in_cython_output
|
|
Description
|
Cython generates .c/.cpp code from a Python-like syntax. Some of it is has
random numbers in it.
|
|
|
Comments:
|
doc/mkhtml.py calls rst2html with the --date argument, embedding
timestamps in html documentation.
.
Some obscure locales used by reprotest trigger reproducibility
issues in html documentation.
.
doc/mkhtml.py embeds the basename of the build directory in
changelog_basename. (changes-4.6.3+dfsg.html vs. changes-2nd.html)
.
versioninfo.py calls os.path.abspath from get_base_dir function,
which outputs an absolute path.
|
| |
|
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).
|