Debian navigation

Notes about issue cmake_rpath_contains_build_path in unstable

Identifier: cmake_rpath_contains_build_path
Suites: stretch / buster / bullseye / unstable / experimental
Description: When an executable is linked with a shared library from the same project,
RPATH will contain the build path. Even if this is stripped on installation,
the build-id will remain unchanged.
Packages can set `-DCMAKE_SKIP_RPATH=ON` as workaround, but then possibly
have to set `LD_LIBRARY_PATH` while running tests.
Alternately with cmake 3.14+, BUILD_RPATH_USE_ORIGIN could be used
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 1 reproducible packages in unstable/amd64: m4api

FTBR icon 1 unreproducible packages in unstable/amd64: x265


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.