]> git.ipfire.org Git - thirdparty/libarchive.git/commit
Fix cpio test in 2038 (#1836)
authorBernhard M. Wiedemann <githubbmw2020@lsmod.de>
Fri, 13 Jan 2023 05:27:42 +0000 (06:27 +0100)
committerGitHub <noreply@github.com>
Fri, 13 Jan 2023 05:27:42 +0000 (21:27 -0800)
commit45c728b00dce4af6b7f0603df0a0af4bafe6f2ad
tree7c5347d9a82babcbe31c5da37926d02ffc3032ff
parent4f2e2e089db86d16aefe2f9d134a0bbb8867408a
Fix cpio test in 2038 (#1836)

Without this patch, `bsdcpio_test_option_c` failed after 2038-01-19 with

```
 .../libarchive-3.6.2/cpio/test/test_option_c.c:143: Assertion failed: t >= now - 2
 .../libarchive-3.6.2/cpio/test/test_option_c.c:169: Assertion failed: t >= now - 2
 .../libarchive-3.6.2/cpio/test/test_option_c.c:205: Assertion failed: t >= now - 2
```

Background:
As part of my work on reproducible builds for openSUSE, I check that
software still gives identical build results in the future.
The usual offset is +16 years, because that is how long I expect some
software will be used in some places.
This showed up failing tests in our package build.
See https://reproducible-builds.org/ for why this matters.
cpio/test/test_option_c.c