Source: radsecproxy Version: 1.10.0-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi, Whilst working on the Reproducible Builds effort [0], we noticed that radsecproxy could not be built reproducibly. This was because it embedded the current build date in the manual pages. A patch is attached that seeds this from SOURCE_DATE_EPOCH (if available). [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
--- a/debian/patches/reproducible-build 1970-01-01 01:00:00.000000000 +0100 --- b/debian/patches/reproducible-build 2023-11-17 08:43:16.864943941 +0000 @@ -0,0 +1,15 @@ +Description: Make the build reproducible +Author: Chris Lamb <la...@debian.org> +Last-Update: 2023-11-17 + +--- radsecproxy-1.10.0.orig/configure.ac ++++ radsecproxy-1.10.0/configure.ac +@@ -12,7 +12,7 @@ AC_PROG_RANLIB + AC_CHECK_FUNCS([mallopt]) + AC_REQUIRE_AUX_FILE([tap-driver.sh]) + +-RELEASEDATE=m4_esyscmd([date +%Y-%m-%d]) ++RELEASEDATE=m4_esyscmd([date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}" +%Y-%m-%d]) + AC_SUBST(RELEASEDATE) + + m4_version_prereq(2.70, [], [AC_PROG_CC_C99]) --- a/debian/patches/series 2023-11-17 08:31:01.036451991 +0000 --- b/debian/patches/series 2023-11-17 08:43:15.736942848 +0000 @@ -1 +1,2 @@ fix-spelling +reproducible-build