Debian navigation

Notes about issue captures_build_path_in_beam_files in unstable

Identifier: captures_build_path_in_beam_files
Suites: stretch / buster / unstable / experimental
Description: Erlang beam files contain the beam path, in a field apparently named "source".
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

FTBFS icon 2 FTBFS packages in unstable/amd64: erlang-cherly erlang-ranch

FTBR icon 39 unreproducible packages in unstable/amd64: ejabberd erlang-asciideck erlang-base64url erlang-bitcask erlang-cf erlang-cl erlang-cowboy erlang-cowlib erlang-cuttlefish erlang-folsom erlang-getopt erlang-goldrush erlang-jiffy erlang-jose erlang-lager erlang-luerl erlang-meck erlang-p1-cache-tab erlang-p1-eimp erlang-p1-iconv erlang-p1-mysql erlang-p1-oauth2 erlang-p1-pam erlang-p1-pgsql erlang-p1-sip erlang-p1-sqlite3 erlang-p1-stringprep erlang-p1-stun erlang-p1-tls erlang-p1-utils erlang-p1-xml erlang-p1-xmpp erlang-p1-yaml erlang-p1-zlib erlang-proper erlang-redis-client erlang-uuid tsung wings3d

 

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.