Debian navigation

Notes about issue gcc_captures_build_path in experimental

Identifier: gcc_captures_build_path
Suites: unstable / trixie / bookworm / bullseye / experimental
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.
Packages in 'experimental' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 17 reproducible packages in experimental/amd64: cubew cyrus-imapd discover gdal gimp gnucap krb5-auth-dialog lensfun ncbi-vdb povray qtimageformats-opensource-src ros-bond-core signond sra-sdk tlsh uw-imap vte2.91

FTBFS icon 9 FTBFS packages in experimental/amd64: autogen budgie-desktop daq darkice dolphin-emu freebayes libgpiv reiser4progs scap-workbench

FTBR icon 3 unreproducible packages in experimental/amd64: moarvm psi-plus qemu

E404 icon 1 404 packages in experimental/amd64: dolfin

depwait icon 2 depwait packages in experimental/amd64: critterding urjtag

 

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.