Reproducible Buildsappview XRPC

liggghts 3.8.0+repack1-16 debian

liggghts_3.8.0+repack1-16_arm64.debsha256 4ef80649d277d27c3001cdd91788f59c26b62c7e9ed09c9266dbcbb05d8b4788

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

2 records, newest first
Builder
rebuilderd.xpam.pl (Debian) via bridgedid:web:rebuilderd.xpam.pl.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-10-25 07:41 UTC
Attestationnonerebuilders attest only byte-identical results
Evidence
at://did:web:rebuilderd.xpam.pl.rbld.dev/org.reproducible-builds.rebuild/4ef80649d277d27c3001cdd91788f59c26b62c7e9ed09c9266dbcbb05d8b4788
Builder
reproduce.debian.net (arm64, armhf) via bridgedid:web:arm64.reproduce.debian.net.rbld.dev
Outcomefailed no rebuilt artifact
finished 2026-09-10 20:38 UTC
Attestationnonerebuilders attest only byte-identical results
Evidence
at://did:web:arm64.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/4ef80649d277d27c3001cdd91788f59c26b62c7e9ed09c9266dbcbb05d8b4788

reproducible-notes

source package liggghts
noted at version 3.4.0+repack1-2
build_id_differences_only
The Build ID differs, but there are no other differences. . Specifically, NT_GNU_BUILD_ID, .gnu_debuglink, and /usr/lib/debug/build-id/* filenames differ, but there are no other differences. . [On 'sope' seen also a difference in a .GCC.command.line section; compare 'records_build_flags'.] . If there _are_ other differences (or if diffoscope output is truncated), don't tag with this issue, but look for the root problem, as explained under build_id_variation_requiring_further_investigation. . When this occurs on unstable but not on testing, it's likely a form of captures_build_path. If it uses the cmake buildsystem, very likely to be cmake_rpath_contains_build_path.
cmake_rpath_contains_build_path more
When an executable is linked with a shared library from the same project, RPATH will contain the build path. Even if this is stripped on installation, the build-id will remain unchanged. . With CMake 3.14+, packages can set `-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON` to fix the issue. This is done automatically when using debhelper compat level v14. https://cmake.org/cmake/help/latest/prop_tgt/BUILD_RPATH_USE_ORIGIN.html . When working with older CMake versions, the `CMAKE_SKIP_RPATH` option can be enabled instead, but it may be required to also set `LD_LIBRARY_PATH` while running tests.
rpath issue fixed by -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON
.
timestamp and username captured in libliggghts.so.*