Hi, lamby has a patch:
commit 60bb20a43218c6ac4b95fd7971026ac0ba5ce682
Author: Chris Lamb <la...@debian.org>
Date: Tue Nov 15 11:25:28 2016 +0000
Build even further in the future to catch more non-determinstic
behaviour.
* Ensure that more bytes of a year changes (eg. 2016->2017 vs.
* 2026->2027)
* Catch FTBFS within the lifetime of the stable release.
* -days 3650 is quite common when generating certicates, so we
* catch FTBFS
this way.
with this change:
- sudo date --set="+398 days +6 hours + 23 minutes"
+ sudo date --set="+3980 days +6 hours + 23 minutes"
I'm not sure but I think that's too much. I think the lifetime of a
stable release is ~5 years, at least after the release, so maybe 7 years
or so, but not 10. Also I'm not sure we deliberatly wont to break stuff
with >3650 days anyway…
So I'd rather propose 2555+31+2=2588 days…
What do you think?
--
cheers,
Holger
signature.asc
Description: Digital signature
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
