Debian navigation

Notes about issue ocaml_captures_build_path in unstable

Identifier: ocaml_captures_build_path
Suites: stretch / buster / bullseye / unstable / experimental
Description: Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 79 reproducible packages in unstable/amd64: belenios camlp4 camlpdf camomile cmdliner coinst cppo cryptgps facile findlib jsonm lwt-log lwt-ssl obus ocaml-astring ocaml-base64 ocaml-batteries ocaml-benchmark ocaml-charinfo-width ocaml-cry ocaml-csv ocaml-domain-name ocaml-dssi ocaml-dtools ocaml-duppy ocaml-expect ocaml-faad ocaml-ffmpeg ocaml-fileutils ocaml-flac ocaml-fmt ocaml-frei0r ocaml-gen ocaml-gstreamer ocaml-inifiles ocaml-lastfm ocaml-libvirt ocaml-lo ocaml-migrate-parsetree ocaml-mm ocaml-num ocaml-ogg ocaml-opus ocaml-parsexp ocaml-portaudio ocaml-ptmap ocaml-qtest ocaml-re ocaml-rope ocaml-sedlex ocaml-shine ocaml-speex ocaml-stdcompat ocaml-taglib ocaml-theora ocaml-visitors ocaml-voaacenc ocaml-vorbis ocamlcreal ocamldap ocamlify ocamlmod ocp-indent ocplib-endian ocsigenserver pagodacf ppx-deriving ppx-optcomp ppx-tools ppx-tools-versioned pxp react reactivedata uuidm wyrd xstr xstrp4 yojson zed

FTBFS icon 4 FTBFS packages in unstable/amd64: camljava liquidsoap ocaml-reins ocaml-res

FTBR icon 32 unreproducible packages in unstable/amd64: apron camlidl camlimages camlzip easy-format lambda-term mlgmp morbig ocaml-alsa ocaml-atd ocaml-bigarray-compat ocaml-bitstring ocaml-ctypes ocaml-dune ocaml-extunix ocaml-gettext ocaml-graphics ocaml-inotify ocaml-ipaddr ocaml-lame ocaml-sqlite3 ocaml-ssl ocaml-trie ocaml-usb ocamlagrep ocamlsdl ocplib-simplex parmap perl4caml syslog-ocaml why3 ocamlgsl#

 

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.