summaryrefslogtreecommitdiffstats
path: root/changelogs
diff options
context:
space:
mode:
authorStefano Rivera <github@rivera.za.net>2024-12-05 23:26:58 +0100
committerGitHub <noreply@github.com>2024-12-05 23:26:58 +0100
commitd500354798beb9bf8341eb8e84e1e2046bbfd21b (patch)
tree8133714a62c5f1f32797e0a97512d8e82a8a859b /changelogs
parentwait_for_connection - test connection=local does not emit warning (#84438) (diff)
downloadansible-d500354798beb9bf8341eb8e84e1e2046bbfd21b.tar.xz
ansible-d500354798beb9bf8341eb8e84e1e2046bbfd21b.zip
unarchive: Clamp zip timestamps on 32-bit time_t (#84409)
Clamp zip timestamps to representible values when unpacking zip files on platforms that use 32-bit time_t (e.g. Debian i386). This is a non-issue in practice (in 2024), but should allow the test suite to pass on Debian i386. We use a round value of 2038-01-01 00:00:00 for simplicity, and to avoid running into timezone offsets closer to the actual limit. MR #81520 introduced sanity-checking tests that used dates not representable with a 32-bit time_t.
Diffstat (limited to 'changelogs')
-rw-r--r--changelogs/fragments/unarchive_timestamp_t32.yaml3
1 files changed, 3 insertions, 0 deletions
diff --git a/changelogs/fragments/unarchive_timestamp_t32.yaml b/changelogs/fragments/unarchive_timestamp_t32.yaml
new file mode 100644
index 0000000000..969c85de05
--- /dev/null
+++ b/changelogs/fragments/unarchive_timestamp_t32.yaml
@@ -0,0 +1,3 @@
+---
+bugfixes:
+ - unarchive - Clamp timestamps from beyond y2038 to representible values when unpacking zip files on platforms that use 32-bit time_t (e.g. Debian i386).