Matthew Woehlke <[EMAIL PROTECTED]> wrote: > ...any news here? I'm not anxious to upgrade tar when it fails half of > its test suite.
Yes, there are. Of 28 failed tests 18 failed because time stamps on your NFS mounted directory are out of sync with the machine where the test was run. In this case tar issues these warning messages on its stderror: tar: directory/file: time stamp 2007-03-07 09:57:12 is 157.337963 s in the future tar: directory: time stamp 2007-03-07 09:57:12 is 157.337416 s in the future which the testsuite does not expect to see. The tests related to incremental backups (9 tests) and fail due to the same reason (each created file becomes `new' or `changed' for the next tar run). The remaining test (#55 -- sparse03.at) fails because cmp reports I/O error: +cmp: sparsefile: Input/output error Thus, none of the failures is related to tar itself. Regards, Sergey
