Reproducible Buildsappview XRPC

asmixer 0.5-16.1 debian

asmixer_0.5-16.1_amd64.debsha256 1b8b379859089dd7e2107a3a5f1888e4945a6c5171c79990e11876eccc7b9693

unverified

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

reproduce.debian.net (amd64) via bridge 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 (amd64) via bridgedid:web:amd64.reproduce.debian.net.rbld.dev
counts toward the verdict
Outcomereproduced rebuilt 1b8b37985908… = target
finished 2024-12-11 00:11 UTC
Attestationverifiedkey did:web:amd64.reproduce.debian.net.rbld.dev#daemon
at://did:web:amd64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/1b8b379859089dd7e2107a3a5f1888e4945a6c5171c79990e11876eccc7b9693

reproducible-notes

source package asmixer
noted at version 0.5-14
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.