Debian navigation

Notes about issue randomness_in_postgres_opcodes in unstable

Identifier: randomness_in_postgres_opcodes
Suites: unstable / trixie / bookworm / bullseye / experimental
Description: randomness in bc files
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 31 reproducible packages in unstable/amd64: bgw-replstatus extra-window-functions ip4r jsquery pg-auto-failover pg-dirtyread pg-fact-loader pg-failover-slots pg-rage-terminator pg-rational pg-show-plans pg-similarity pg-snakeoil pg-squeeze pgauditlogtofile pgfincore pglogical pglogical-ticker pgpcre pgsql-asn1oid pgsql-ogr-fdw pldebugger plprofiler postgresql-mysql-fdw postgresql-periods postgresql-plproxy postgresql-q3c postgresql-unit tablelog toastinfo wal2json

FTBFS icon 4 FTBFS packages in unstable/amd64: llvm-toolchain-14 pgl-ddl-deploy postgresql-numeral repmgr

FTBR icon 2 unreproducible packages in unstable/amd64: postgresql-debversion rdkit

 

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.