Notes about issue build_id_differences_only in experimental
| Identifier: | build_id_differences_only |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
The Build ID differs, but there are no other differences. . Specifically, NT_GNU_BUILD_ID, .gnu_debuglink, and /usr/lib/debug/build-id/* filenames differ, but there are no other differences. . [On 'sope' seen also a difference in a .GCC.command.line section; compare 'records_build_flags'.] . If there _are_ other differences (or if diffoscope output is truncated), don't tag with this issue, but look for the root problem, as explained under build_id_variation_requiring_further_investigation. . When this occurs on unstable but not on testing, it's likely a form of captures_build_path. If it uses the cmake buildsystem, very likely to be cmake_rpath_contains_build_path. |
|
Packages in 'experimental' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
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.