On Mon, Mar 31, 2025 at 11:17:15AM +0100, Chris Lamb wrote:
+-RELEASE_DATE=`date -r $0 +%F` ++RELEASE_DATE=m4_esyscmd([date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}" +%Y-%m-%d])
did you even try to understand what the upstream code does, and why it fails here? the problem is that debian re-generates configure each time, thus falsifying the release timestamp. it should use a different reference, probably debian/changelog. upstream, i might switch to NEWS, given commit ea22b09ac in master. that would be a bit uglier for git builds, though. VERSION would be better in this regard. would this be compatible with the debian build process?
