Debian navigation

Notes about issue captures_build_path_via_assert in unstable

Identifier: captures_build_path_via_assert
Suites: stretch / buster / unstable / experimental
Description: Absolute paths to source file names are embedded through assert(), which
embeds the value of the __FILE__ macro in the .data section, or via
filenames in debug symbols, which shows in the .text and .debug_str sections.
.
We have a pending patch to GCC to fix this in one central place.
.
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html
.
If/when this is accepted, this issue should be fixed for all packages and
you should not need to fix it specifically in your package.
.
For more background information see:
.
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

unreproducible icon 18 unreproducible packages in unstable/amd64: apper biboumi clsparse dune-grid fifechan kaccessible limesuite lsyncd ros-opencv-apps spell subversion ufo-core uftrace unshield compiz# freerdp2# nginx# purify#

FTBFS icon 3 FTBFS packages in unstable/amd64: pldebugger libreswan# tiledarray#

reproducible icon 23 reproducible packages in unstable/amd64: ableton-link blasr btrfs-progs cryfs dune-geometry dune-grid-glue dune-uggrid hhsuite ir.lv2 jstest-gtk kdiagram kmer muparserx ngraph-gtk openvas-cli openzwave php-apcu qmc simpleparse sopt supercollider-sc3-plugins tessa ntopng#

 

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

A package name displayed with a bold font is an indication that this package has a note. Visited packages are linked in green, those which have not been visited are linked in blue.
A # sign after the name of a package indicates that a bug is filed against it. Likewise, a + sign indicates there is a patch available, a P means a pending bug while # indicates a closed bug. In cases of several bugs, the symbol is repeated.