Reproducible Buildsappview XRPC

lam-mpidoc 7.1.4-7.2 debian

lam-mpidoc_7.1.4-7.2_all.debsha256 4490604ae441d30c9ea12ae1a1c92f9d92d3995dd5d76e099bca2fecb17d480a

unverified

0 of 1 required independent builders reproduced this artifact bit for bit, each with an attestation signed by a key its DID document declares.

one more verified builder
threshold
123
distinct builders; the first-party build never counts

Claims by builder

1 record, newest first
Builder
reproduce.debian.net (all) via bridgedid:web:all.reproduce.debian.net.rbld.dev
Outcomefailed no rebuilt artifact
finished 2026-03-01 02:51 UTC
Attestationnonerebuilders attest only byte-identical results
Evidence
at://did:web:all.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/4490604ae441d30c9ea12ae1a1c92f9d92d3995dd5d76e099bca2fecb17d480a

reproducible-notes

source package lam
noted at version 7.1.4-3.1, bugs #1021469
timestamps_in_gzip_headers more
gzip stores a timestamp by default in its header.
user_hostname_manually_added_requiring_further_investigation
Packages which intentionally capture the username or hostname into a custom format, but aren't obviously using any tool or system which has this as a core issue. Interesting because they could be fixed by fixing these things at build time.
captures_shell_variable_in_autofoo_script
Something looking like autotools is capturing SHELL for use at runtime, which should probably be fixed to /bin/sh anyway. . Autotools also capturing the build path.
random_order_in_static_libraries
order of members in a static library change between build1 and build2
captures_build_path
Captures build path, e.g., /build/1st/foo-42.0 v. /build/foo-42.0/2nd . Until early 2024 we varied the build path when testing packages from unstable and experimental, which we have stopped doing now as the build path is recorded as part of the environment and thus can be used when rebuilding. . This issue is kept here for the time being. . This issue is only for miscellaneous issues which need individual fixes, please create new issues for specific issues, e.g. gcc_captures_build_path. . Here follows some general tips for packages using the standard GNU toolchain: . If using autoconf, make sure you call ./configure via a relative and not absolute path. . If your issue is related to using the `__FILE__` macro, or the recording of --debug-prefix-map flags in non-GCC non-debugging output, this is what is fixed by our patch mentioned above; you should not need to fix it specifically in your package. . For more background information see: . • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html This package list is currently incomplete, as the issue was incorrectly marked as deterministic
Embed build time, hostname, and username in
/usr/include/lam/lam_build_info.h,
/usr/share/doc/lam4-dev/examples/config.status.gz,
/usr/share/doc/lam4-dev/examples/config/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/alltoall/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/cxx/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/fault/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/hello/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/mandelbrot/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/pi/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/ring/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/romio/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/topology/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/trivial/Makefile.gz,
/usr/share/doc/lam4-dev/examples/main/wave1d/Makefile.gz.