Reproducible Buildsappview XRPC

libapt-pkg-doc 3.3.7 debian

libapt-pkg-doc_3.3.7_all.debsha256 0167c6f80c1f0e72e0d9b86d54be7bea38823e2799688afa947af1e4343f856f

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 (all) via bridgedid:web:all.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-11-11 15:58 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:all.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/0167c6f80c1f0e72e0d9b86d54be7bea38823e2799688afa947af1e4343f856f

reproducible-notes

source package apt
noted at version 1.4.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.
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.
nondeterminstic_todo_identifiers_in_documentation_generated_by_doxygen
eg. '<a class="anchor" id="_todo000056"> vs <a class="anchor" id="_todo000058">'
nondeterministic_ordering_in_documentation_generated_by_doxygen
"Additional Inherited Members" has nondeterministic children in the (HTML?) docs. . This can also happen when there is a real C function and a hash-define with the same name. Doxygen sorts the member names but it only appears to use the name so it is not stable relative to their type, resulting in nondeterministic output. . MemberNameSDict::compareValues in doxygen's membername.cpp is suspicious.
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.
Passing -ffile-prefix-map appears to remove the build path, but if
the path length differs (e.g. /build/1234 vs. /build/123456), the
size of the empty padded data will still differ.
.
rpath issue fixed by -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON