Reproducible Buildsappview XRPC

r-cran-brio 1.1.5-1 debian

r-cran-brio_1.1.5-1_armhf.debsha256 012bacf33e0d2ede7a29de3c540001a3a27a1ae70c183521342d069caccd7892

unverified

0 of 3 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 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-04 19:02 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/012bacf33e0d2ede7a29de3c540001a3a27a1ae70c183521342d069caccd7892

reproducible-notes

source package r-cran-brio
noted at version 1.1.0-2
randomness_in_r_rdb_rds_databases
R creates .rdb files and .rds with some randomness. They are a serialisation of some sorts, related to lazy loading of modules? Randomness seems to come from using absolute paths in .rd[bs] files. . Is not related to https://bugs.debian.org/774031 / r_base_appends_built_header_to_description_files . We have a pending patch to fix most of these (463/478) packages at the time of writing) upstream in R: . https://stat.ethz.ch/pipermail/r-devel/2017-April/074138.html . When this is accepted into R upstream, commit 28d4af25 may be (un-)reverted to remove these packages. In the meantime, please do not remove this issue, nor mark it as deterministic, nor untag these packages. . The remaining ~15 packages are not completely fixed by this patch, so this issue should remain, even when our upstream patch is accepted. These packages will need to be investigated and fixed individually, see our blog post on how to do that: . https://reproducible-builds.org/news/2017/05/03/reproduciing-r-packages/