Notes about issue graphviz_nondeterministic_output in unstable
Identifier: | graphviz_nondeterministic_output |
---|---|
Suites: | unstable / trixie / bookworm / bullseye / experimental |
Description: |
graphviz appears to use a non-deterministic algorithm to optimally lay out notes optimally. This can appear in class hierarchy documentation, etc. Can presumably affect images of all complexity but, obviously, more likely to affect images with lots of nodes. . see https://twitter.com/Graphviz/status/1039632469782396929 |
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
11 reproducible packages in unstable/amd64:
2 FTBFS packages in unstable/amd64:
3 unreproducible packages in unstable/amd64:
|
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.