Debian navigation

Notes about issue nondeterministic_ordering_in_guile_binaries in buster

Identifier: nondeterministic_ordering_in_guile_binaries
Suites: unstable / trixie / bookworm / bullseye / buster / experimental
Description: The ordering of various procedures in guile .go files can vary
when built in parallel. Can be worked around by disabling
parallelism in the build process.
.
Symtoms may include wrapXXX-procedures with different numbering
and/or a reference to SOMEFILE.scm present in one build but not
the other.
.
https://bugs.debian.org/995092
https://github.com/NixOS/nixpkgs/pull/78778
https://issues.guix.gnu.org/issue/20272
https://build.opensuse.org/request/show/732638
Packages in 'buster' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 1 reproducible packages in buster/amd64: guile-lib

FTBR icon 1 unreproducible packages in buster/amd64: guile-2.2

 

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.