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

reproducible icon 21 reproducible packages in experimental/amd64: bacula cubew cyrus-imapd darktable flexbar gnucap haproxy kbd krb5-auth-dialog lensfun liblopsub linux ncbi-vdb nix oxygen povray tlsh udisks2 vdr-plugin-epgsearch vdr-plugin-streamdev bind9#

FTBFS icon 5 FTBFS packages in experimental/amd64: autogen darkice freebayes libgpiv scap-workbench

FTBR icon 1 unreproducible packages in experimental/amd64: intel-graphics-compiler

depwait icon 4 depwait packages in experimental/amd64: critterding daq reiser4progs 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.