Reproducible Buildsappview XRPC

r-bioc-xvector 0.46.0-2 debian

r-bioc-xvector_0.46.0-2_amd64.debsha256 0102689cb55e711c007fe5d06526e2bb8e50b30ac97973ec4491b064fcca153f

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 (amd64) via bridgedid:web:amd64.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-02-26 18:43 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:amd64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/0102689cb55e711c007fe5d06526e2bb8e50b30ac97973ec4491b064fcca153f

reproducible-notes

source package r-bioc-xvector
noted at version 0.12.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/
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.