Reproducible Buildsappview XRPC

r-cran-lwgeom 0.2-14-1 debian

r-cran-lwgeom_0.2-14-1_armhf.debsha256 422d4f4b02feda17c76cc707bc0f7a10671d3a9121c9c909899907d47e6f3d83

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
Outcomefailed no rebuilt artifact
finished 2026-03-01 20:10 UTC
Attestationnonerebuilders attest only byte-identical results
Evidence
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/422d4f4b02feda17c76cc707bc0f7a10671d3a9121c9c909899907d47e6f3d83

reproducible-notes

source package r-cran-lwgeom
noted at version 0.1-4+dfsg-1
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/