Debian navigation

Notes about issue ftbfs_due_to_f-file-prefix-map in unstable

Identifier: ftbfs_due_to_f-file-prefix-map
Suites: stretch / buster / bullseye / unstable / experimental
Description: An example of failure related to this are programs that expect
__FILE__ to expand to some absolute path, but instead finding themselves
a relative one.
In our unstable and experimental build systems we export
that makes dpkg-buildflags enable the reproducible/fixfilepath feature, adding
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: golang-github-howeyc-fsnotify

FTBFS icon 33 FTBFS packages in unstable/amd64: appstream atlas-ecmwf chromium httping libblocksruntime python-kubernetes seqan thunderbird analitza+ catch2+ cgreen+ fuzzylite+ gloo+ grantlee5+ ignition-common+ kalarmcal+ kcodecs+ kdeclarative+ keditbookmarks+ kitemmodels+ kookbook+ kparts+ libkf5kgeomap+ libkgapi+ llvm-toolchain-9+ massif-visualizer+ okteta+ openorienteering-mapper+ scram+ seqan2+ simde+ tellico+ vboot-utils++

FTBR icon 3 unreproducible packages in unstable/amd64: firmware-microbit-micropython knotifications qtremoteobjects-everywhere-src


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.