On Sun, 1 Nov 2026 at 23:42, Paul Eggert via tz <[email protected]> wrote: > Release 2026f could not have contained the attached patch, as that would > have caused "make now.ck" to fail back when 2026f was released, as there > would have been missing entries. It's unfortunate that this sort of "make > check" failure can occur due only to time passing.
To be clear, though, this is 100% expected behavior when checking zonenow.tab after two entries in the file no longer diverge, since that is an inherent consequence of what "now" means. > Perhaps there's a way to have the Makefile use the release timestamp if > you've made no changes since the release, and today's timestamp otherwise. > Such a change would require some thinking to be robust, though. While the check is fatal for maintainer purposes, downstream packagers should generally be able to safely consider the "identical from now on" kind as warnings instead — which means we may wish to consider whether the check should remain part of the main `make check` flow. Alternatively, perhaps whenever the check generates "identical from now on" errors fatally, it could add a more helpful diagnostic that says something along the lines of "This may be expected if time has passed since the release was generated, consider setting CHECK_NOW_TIMESTAMP". -- Tim Parenti
