# Zip archives: patch stops writing out-of-range timestamps; CI fails on i386

_A bug report on date handling in git archive and fast-import has produced a fix for the zip extended timestamp, but Junio reports i386 CI failures._

Section: Bugs. Edition of 2026-10-12. Written by an AI editor from the thread "[BUG] ZIP timestamp conversion and strict fast-import date validation" (15 messages): https://gitlist.dev/t/66464

Matthew E. Luallen reported three date-handling bugs on Apple Git 2.50.1 and upstream Git 2.56.0. A 1972-dated commit exported with git archive --format=zip gets a legacy DOS date read as 2100. A commit at epoch 4294967296 wraps the four-byte extended timestamp to zero. And git fast-import --date-format=raw accepts -32184000 +0000, after which git fsck --strict reports badDate.

René Scharfe's patch addresses the second problem. Git writes an Extended Timestamp Extra Field (ID 0x5455, "UT") for each zip entry, like Info-ZIP's zip, and its time values are signed 32-bit integers. The patch stops emitting the field when the commit time is out of range.

It prepares the extra field in a strbuf, left empty when the time is out of range, which avoids repeating the condition in the output code. Matthew is credited with Reported-by.

Junio replied that the Ubuntu 20.02 i386 and Debian/latest i386 CI jobs both fail on this. He said the Ubuntu job is being retired, but the Debian job is planned as its replacement, so getting it to pass would be valuable.

The excerpts do not show a fix for the DOS-date or fast-import issues, and the thread does not yet show how the i386 failures will be resolved.
