Incorrect mtime serialization in tar archives

[archiverjs]

Incorrect mtime serialization in tar archives

[ctalkington]

thanks for the report. will investigate this weekend.

[ctalkington]

im wondering if its a difference in specs. I have been going by gnu tar specs here:

http://www.gnu.org/software/tar/manual/html_node/Standard.html

The name, linkname, magic, uname, and gname are null-terminated character strings. All other fields are zero-filled octal numbers in ASCII. Each numeric field of width w contains w minus 1 digits, and a null.

[ctalkington]

Looking at what I believe is the project your talking about:

http://commons.apache.org/proper/commons-compress/tar.html

The tar package does not support the full POSIX tar standard nor more modern GNU extension of said standard.

[VladRassokhin]

Hm. Ok.
Yes, it's about reading tar with apache-commons-compress.

BTW: Each numeric field of width w contains w minus 1 digits, and a null
So i believe my request still actual :)

[ctalkington]

ah seems I must of left out the null part. most tar parsers are too forgiving and verify even if they don't match spec exactly. working on few aspects but should get an update out this week to resolve the issue.

[ctalkington]

sorry for the delay. v0.4.10 has been pushed out.