Reproducible Buildsappview XRPC

libf77dcl7 7.5.2-1 debian

libf77dcl7_7.5.2-1_arm64.debsha256 01052099754eae2ec928298d962688234da2dfa1c8c247bd108deca3ff90bee5

unverified

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

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

Claims by builder

1 record, newest first
Builder
reproduce.debian.net (arm64, armhf) via bridgedid:web:arm64.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-03-05 08:52 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/01052099754eae2ec928298d962688234da2dfa1c8c247bd108deca3ff90bee5

reproducible-notes

source package dcl
noted at version 7.3.3-1
gcc_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. . dpkg-buildflags version 1.20.6+ sets -ffile-prefix-map by default (and -fdebug-prefix-map in older versions) which fixes this issue in many cases, but not all (see: records_build_flags). . There are patches submitted upstream to address this specific issue, but they are unlikely to be merged at this point: . https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html . When this is accepted into GCC upstream, we could remove this note. In the meantime, please do not remove this issue, nor mark it as deterministic, nor untag these packages.