Notes about issue build_id_variation_requiring_further_investigation in unstable
|Suites:||stretch / buster / bullseye / unstable / experimental|
ld adds a Build ID in ELF binaries used to link external debug symbols.
See https://fedoraproject.org/wiki/Releases/FeatureBuildId#Unique_build_ID for
The default value is a SHA1 hash over the content of the binary. See
the `--build-id` option in https://sourceware.org/binutils/docs-2.25/ld/Options.html
for other behavior.
Unless a different way to compute Build IDs has been specified, different Build IDs
are the symptom of different binary content. The actual source of the
difference might not be visible because the debug symbols might have been stripped
(and they can contain filenames which can differ if the build path is different).
There is no general solution for this problem. The source of the variation must
be tracked and fixed. The issue can come from variations in order of object
members or objects themselves, different content (e.g. `__DATE__` CPP
macros or similar), or other interesting things.
Please don't tag issues with this issue until I find a place for this text ^
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)
1 FTBFS packages in unstable/amd64:
29 unreproducible 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.
# 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.