Notes about issue berkeley_db_variation_requiring_further_investigation in unstable
| Identifier: | berkeley_db_variation_requiring_further_investigation |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| URL: | https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20150302/001188.html |
| Description: |
Berkeley databases are not reproducibly. This issue requires further poking to understand way. https://github.com/libzhuyin/libzhuyin/issues/7 |
|
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
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.