|
From: | Paul Eggert |
Subject: | Re: [Bug-tar] tar writes invalid mtime for times before the epoch |
Date: | Sat, 18 Nov 2017 08:48:14 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 |
Rodrigo Queiro wrote:
I discovered this because Python's tarfile module fails to open such files with "invalid header", since it expects this field to contain an ASCII number, as described in the docs:
That's a shortcoming in tar's documentation. Tar uses the GNU format by default, which has a base-256 extension that supports negative timestamps. If you want GNU tar to refuse to use this GNU extension, please use '-H ustar'.
I fixed the documentation bug by installing the attached patches. Most of them are to bring Tar up-to-date with recently-released compilers and whatnot; patch 0003 fixes the documentation bug in question.
0001-Fix-typo-caught-by-GCC-7.2.1.patch
Description: Text Data
0002-build-update-gnulib-submodule-to-latest.patch
Description: Text Data
0003-Document-base-256-representation-in-GNU-format.patch
Description: Text Data
0004-Port-to-Texinfo-6.4.patch
Description: Text Data
0005-Port-to-gcc-Wimplicit-fallthrough-5.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |