Reproducible Buildsappview XRPC

grass-core 8.4.1-1 debian

grass-core_8.4.1-1_armel.debsha256 0219d8d3dbfca00c7b5d593c2431523900da4771bf7832a500996e6b76e0bcbc

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 (armel) via bridgedid:web:armel.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-05-23 15:12 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:armel.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/0219d8d3dbfca00c7b5d593c2431523900da4771bf7832a500996e6b76e0bcbc

reproducible-notes

source package grass
noted at version 7.0.4-3
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. . This issue is only for miscellaneous issues which need individual fixes, please create new issues for specific issues, e.g. gcc_captures_build_path. . Here follows some general tips for packages using the standard GNU toolchain: . If using autoconf, make sure you call ./configure via a relative and not absolute path. . If your issue is related to using the `__FILE__` macro, or the recording of --debug-prefix-map flags in non-GCC non-debugging output, this is what is fixed by our patch mentioned above; 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 This package list is currently incomplete, as the issue was incorrectly marked as deterministic
records_build_flags
Records $CFLAGS, which vary intentionally due to the «-fdebug-prefix-map=${BUILDPATH}=.», «-ffile-prefix-map=${BUILDPATH}=.» or «-fmacro-prefix-map=${BUILDPATH}=.» flags. . We have a patch pending to GCC to fix this issue centrally: . https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html . Though the patch is currently unlikely to be merged. 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. . There is also a work-in-progress patch to dpkg that could address this issue: . https://bugs.debian.org/985553 . 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
timestamps_in_3d_files_created_by_survex
cave surveying files appear to have a UNIX timestamp in their headers
Embeds the build path in /usr/lib/grass70/etc/python/grass/lib/*.py files
https://sources.debian.net/src/grass/7.0.5-1/lib/python/ctypes/ctypesgencore/printer/defaultheader.py/?hl=3#L4
https://sources.debian.net/src/grass/7.0.5-1/lib/python/ctypes/ctypesgencore/printer/printer.py/#L81