Debian navigation

Notes about issue randomness_in_postgres_opcodes in forky

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

reproducible icon 19 reproducible packages in forky/amd64: bgw-replstatus jsquery pg-dirtyread pg-failover-slots pg-rage-terminator pg-show-plans pg-similarity pg-snakeoil pgauditlogtofile pgfincore pglogical pglogical-ticker pgsql-ogr-fdw pldebugger postgresql-debversion postgresql-mysql-fdw postgresql-periods postgresql-q3c postgresql-unit

FTBFS icon 16 FTBFS packages in forky/amd64: extra-window-functions ip4r pg-auto-failover pg-fact-loader pg-rational pg-squeeze pgl-ddl-deploy pgpcre pgsql-asn1oid plprofiler postgresql-numeral postgresql-plproxy repmgr tablelog toastinfo wal2json

 

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.