Debian navigation

Notes about issue captures_varying_number_of_build_path_directory_components in unstable

Identifier: captures_varying_number_of_build_path_directory_components
Suites: stretch / buster / bullseye / unstable / experimental
Description: eg. /tmp/buildd/one/two vs /tmp/buildd/one/two/three can result in relative URIs (eg. ../../../usr/some/share/dir) differing.
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 3 reproducible packages in unstable/amd64: node-srs photutils vue.js

FTBFS icon 1 FTBFS packages in unstable/amd64: node-iconv

FTBR icon 27 unreproducible packages in unstable/amd64: astropy-regions astroscrappy cyvcf2 leaflet-image libgpuarray lumino node-dagre-d3-renderer node-dagre-layout node-es6-promise node-jschardet node-jsonld node-magic-string node-matrix-js-sdk node-modern-syslog node-node-forge node-prop-types node-rdf-canonize node-re2 node-url-parse node-websocket node-zipfile python-pomegranate python-pyspike qutip rainloop twitter-bootstrap4 yt


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.