Reproducible Buildsappview XRPC

libancient-dev 2.2.0-1 debian

libancient-dev_2.2.0-1_amd64.debsha256 1b854d11a24f1e465c4c69f1714455ff2f09dff31fe12eb5fdbccf7792dae2cc

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 1b854d11a24f… = target
finished 2024-09-26 06:00 UTC
Attestationverifiedkey did:web:amd64.reproduce.debian.net.rbld.dev#daemon
at://did:web:amd64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/1b854d11a24f1e465c4c69f1714455ff2f09dff31fe12eb5fdbccf7792dae2cc

reproducible-notes

source package ancient
noted at version 1.0-1
captures_build_path_via_assert
This is not an issue on reproduce.debian.net and no longer done on tests.reproducible-builds.org. . Absolute paths to source file names are embedded through assert(), which embeds the value of the __FILE__ macro in the .data section, or via filenames in debug symbols, which shows in the .text and .debug_str sections. . We have a pending patch to GCC to fix this in one central place. . https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html . If/when this is accepted, this issue should be fixed for all packages and you should not need to fix it specifically in your package. . For more background information see: . • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html