Reproducible Buildsappview XRPC

4g8 1.0-6+b1 debian

4g8_1.0-6+b1_arm64.debsha256 f1c9fdb081b8a76dc08702348276731c3927f6e646ed0f3bae025b647786117a

reproduced

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

reproduce.debian.net (arm64, armhf) via bridge
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
counts toward the verdict
Outcomereproduced rebuilt f1c9fdb081b8… = target
finished 2025-01-31 03:24 UTC
Attestationverifiedkey did:web:arm64.reproduce.debian.net.rbld.dev#daemon
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/f1c9fdb081b8a76dc08702348276731c3927f6e646ed0f3bae025b647786117a

reproducible-notes

source package 4g8
noted at version 1.0-3
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.