Notes about issue captures_build_path in unstable
Identifier: | 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. . 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 |
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
1 reproducible packages in unstable/amd64:
6 FTBFS packages in unstable/amd64:
56 unreproducible packages in unstable/amd64:
1 404 packages in unstable/amd64:
1 build timeout packages in unstable/amd64:
3 not for us packages in unstable/amd64:
|
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.