Debian navigation

Notes about issue captures_build_path_via_assert in trixie

Identifier: captures_build_path_via_assert
Suites: unstable / trixie / bookworm / bullseye / experimental
Description: Absolute paths to source file names are embedded through assert(), which
embeds the value of the __FILE__ macro in the .data section, or via
filenames in debug symbols, which shows in the .text and .debug_str sections.
.
We have a pending patch to GCC to fix this in one central place.
.
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html
.
If/when this is accepted, this issue should be fixed for all packages and
you should not need to fix it specifically in your package.
.
For more background information see:
.
https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html
https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html
https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html
Packages in 'trixie' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 164 reproducible packages in trixie/amd64: ableton-link ancient antimony apper audmes autodock-vina azure-uamqp-python bedtools biboumi btrfs-progs bustools buzztrax c2x ckbuilder compiz cryfs cryptokit dde-calendar dhex dmarc-cat dmrconfig duktape duma dune-uggrid erlang-p1-stringprep estscan etbemon ffmpegfs fhist fifechan fontmatrix freerdp2 fsplib genht gftl-shared git-annex git-repair glulxe gmp gmp-ecm gnucobol hacktv hhsuite holes i3-wm i3status imagination innoextract insserv ir.lv2 ivar jacktrip jstest-gtk kmer lasso libapache2-mod-authn-yolo libcap2 libcrypt-openssl-rsa-perl libesedb libevt libfvde libgclib libjpeg liblnk libmoe libmstoolkit libnxt liboping librandomx libvariable-magic-perl limesuite listserialportsc lltdscan lsyncd lumpy-sv lz4 mapserver mecab mender-client mescc-tools metar minimap2 mujs muparserx netatalk nginx ngraph-gtk ocaml-cstruct ocaml-sha octave-octclip octave-sparsersb orpie peony-extensions pg-bsd-indent pgstat php-apcu pldebugger plotsauce plume-creator pnscan ponyprog prometheus-postfix-exporter protobuf python-pyproj qmc qmidinet qtnetworkauth-everywhere-src qwinff redisearch rng-tools5 ros-opencv-apps rtklib ruby-bindex ruby-bootsnap ruby-character-set ruby-commonmarker ruby-ed25519 ruby-github-linguist ruby-kgio ruby-murmurhash3 ruby-pg-query ruby-rblineprof ruby-rbtrace ruby-strptime ruby-thrift simdjson simka skiboot snek snooze soapdenovo spell ssocr st steghide sumaclust sumatra suricata survivor swarm-cluster systemc tarlz tmd710-tncsetup trinityrnaseq tvoe ufo-core uftrace uisp ukui-media unshield uwsgi vdr-plugin-dvbhddevice vdr-plugin-dvbsddevice vfu vim-command-t vpb-driver vulkan-loader xc3sprog xevil xlunzip kafs-client+ pure-ftpd+ subversion# wiipdf#

FTBFS icon 5 FTBFS packages in trixie/amd64: gap openzwave ruby-bcrypt-pbkdf ruby-regexp-property-values zfs-fuse

FTBR icon 6 unreproducible packages in trixie/amd64: dune-geometry nfdump opensubdiv psychtoolbox-3 spglib zytrax

 

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.