Notes about issue random_order_in_md5sums in unstable
Identifier: | random_order_in_md5sums |
---|---|
Suites: | unstable / trixie / bookworm / bullseye / experimental |
Description: |
order of files in md5sums (in control.tar.gz) differ from build1 to build2. This only happens in packages not using dh_md5sums and it's easily fixed by sorting the output of "find" before piping it to md5sum. Example: . cd debian/tmp && \ find * -type f ! -regex "^DEBIAN/.*" -print0 |\ LC_ALL=C sort -z | xargs -0r md5sum > DEBIAN/md5sums |
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
20 reproducible packages in unstable/amd64:
3 FTBFS packages in unstable/amd64:
2 unreproducible packages in unstable/amd64:
|
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.