| Version annotated: |
5.1.2+dfsg+1-2 |
|
Identified issues:
|
|
Identifier:
|
timestamps_from_cpp_macros
|
|
URL
|
https://wiki.debian.org/ReproducibleBuilds/TimestampsFromCPPMacros
|
|
Description
|
The C pre-processor macros `__DATE__`, `__TIME__`,
capture the current time, and thus will obviously make a build
unreproducible.
|
|
Identifier:
|
diffoscope_runs_forever
|
|
URL
|
https://reproducible.debian.net/index_breakages.html
|
|
Description
|
Some packages cannot be analysed by diffoscope due to it running "forever".
Currently the diffoscope process is killed after 120 minutes.
https://reproducible.debian.net/index_breakages.html collects a list of currently
undiffable packages (as well as other issues with tests.reproducile-builds.org.
|
|
Identifier:
|
blacklisted_on_jenkins
|
|
Description
|
Some packages have been blacklisted in our test infrastructure because
their build hangs, takes too long, spawns processes that are not killed, or
simply because they use too many resources for our current capacity. (This
is purely practical step - we would like to test 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:
|
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.
.
This issue is only for miscellaneous issues which need individual fixes,
please create new issues for specific issues, e.g. gcc_captures_build_path.
.
Here follows some general tips for packages using the standard GNU toolchain:
.
If using autoconf, make sure you call ./configure via a relative and not absolute path.
.
If your issue is related to using the `__FILE__` macro, or the recording of
--debug-prefix-map flags in non-GCC non-debugging output, this is what is
fixed by our patch mentioned above; you should not need to fix it
specifically in your package.
.
For more background information see:
.
• https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html
• https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html
• https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html
|
|
|
Comments:
|
Captures build path using CMAKE_CURRENT_SOURCE_DIR in various CMakeLists.txt
|
| |
|
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).
|