Hi Daniel,
> Chris, are you sure that's right? According to date(1), the --date
> option takes an argument, so that would seem to take "--utc" as the date
> to parse
Mea culpa.
I think what happened was that as it was a patch-to-a-patch I
either a) made the change I attached quasi-manually and I made a
mistake or b) I just screwed up and the error message itself made
the package reproducible.
As in:
date: the argument ‘@1’ lacks a leading '+';
… is, of course, the same in all timezones. *grin*
Updated patch attached. Thanks for your careful review, extremely
appreciated.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
---
a/debian/patches/0001-Use-package-specific-revision-and-date-for-build.patch
2018-10-24 13:50:20.920473047 -0400
---
b/debian/patches/0001-Use-package-specific-revision-and-date-for-build.patch
2018-10-24 13:51:46.254632670 -0400
@@ -91,8 +91,8 @@ build:
@echo "-antigen-env-setup" >> ${TARGET}
@echo "${VERSION}" > ${VERSION_FILE}
@@ -17,7 +15,7 @@
- @$(call ised,"s/{{ANTIGEN_REVISION}}/$$(git log -n1 --format=%h --
src)/",${TARGET})
- @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(git log -n1 --format='%ai'
-- src)/",${TARGET})
+ @$(call ised,"s/{{ANTIGEN_REVISION}}/Debian/",${TARGET})
-+ @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(date --date
@$$(dpkg-parsechangelog -STimestamp) --rfc-3339=seconds)/",${TARGET})
++ @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(date --utc --date
@$$(dpkg-parsechangelog -STimestamp) --rfc-3339=seconds)/",${TARGET})
ifeq (${WITH_DEBUG}, no)
@$(call isede,"s/ (WARN|LOG|ERR|TRACE) .*&//",${TARGET})
@$(call isede,"/ (WARN|LOG|ERR|TRACE) .*/d",${TARGET})
