Reproducible Buildsappview XRPC

fb-modules-6.12.117+deb13-armmp-di 6.12.117-1 debian

fb-modules-6.12.117+deb13-armmp-di_6.12.117-1_armhf.udebsha256 019771d66b8b0210aba5730cc00907f018bc9b108bf687dc894a8dade5b10588

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 (arm64, armhf) via bridgedid:web:arm64.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-11-20 10:20 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/019771d66b8b0210aba5730cc00907f018bc9b108bf687dc894a8dade5b10588

reproducible-notes

source package linux
noted at version 5.2.9-2
randomness_in_documentation_generated_by_sphinx more
Sphinx might output references to memory addresses and generate a json index file with entries in random order or with non-deterministic values (eg. searchindex.js). See https://bugs.debian.org/822197 for memory address issue . searchindex.js needs sort_keys=True (jsonimpl.py) but the key values vary too.
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.
build_path_captured_in_assembly_objects more
This is issue has been fixed for GCC 13 on 2022-11-02. . Before GNU as didn't support BUILD_PATH_PREFIX_MAP, so objects compiled from assembly sources captured the build path. . Before GNU "as" only supported --debug-prefix-map=BUILDPATH=. which can sometimes be passed via ASMFLAGS, ASFLAGS, or similar variables.
linux-perf includes static data tables generated from nftw() callbacks, making it sensitive to directory order.
See source file tools/perf/pmu-events/jevents.c and generated file debian/build/build-tools/tools/perf/pmu-events/pmu-events.c.
.
Build path captured in CONFIG_SYSTEM_TRUSTED_KEYS in various fiels in linux-headers-X.Y.Z packages, via use of CURDIR
https://sources.debian.org/src/linux/6.1.20-2/debian/bin/gencontrol.py/#L595