Debian navigation

Notes about issue randomness_in_objects_inv in buster

Identifier: randomness_in_objects_inv
Suites: unstable / trixie / bookworm / bullseye / buster / experimental
Description: Some Python documentation tool writes objects.inv files in a random order.
.
There is also a translation issue that is being tracked in sphinxdoc_translations
Packages in 'buster' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 47 reproducible packages in buster/amd64: copyq cvxopt factory-boy gdspy glances liborcus libserial logzero mailman3 mathjax-docs mopidy mutagen openshot-qt pikepdf postorius pygccjit pymodbus pyqt5 pyserial-asyncio pysoundfile pytest-qt python-aioamqp python-attrs python-cssselect2 python-django-crispy-forms python-dtcwt python-dugong python-flask-cors python-ilorest python-josepy python-libevdev python-midiutil python-psutil python-pykka python-ruffus python-semantic-version python-tinycss2 python-twitter pytools quodlibet scapy snakemake stressant subuser terminaltables todoman twine

FTBFS icon 1 FTBFS packages in buster/amd64: python-whoosh

 

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.