When reading a file larger than about 2 GB in a tar file, tar claims that the file size is negative; e.g. $ tar tfvv /tmp/! -rw-r----- 236/236 -1751465006 Aug 1 15:13 2000 bigfile tar: Skipping to next file header... Fix: I assume that someone is treating the size as a signed int when they shouldn't be. For what it's worth, GNU tar 1.13 can read the file in question. How-To-Repeat: Make a big file. Tar it. Untar it.
This hirts me too. Dmitry
This appears to be a duplicate of bug #28820
Responsible Changed From-To: freebsd-bugs->mjacob I'll take it for the moment.
Responsible Changed From-To: mjacob->freebsd-bugs I don't have time to work on this in the way it should be done.
Please close the PR due to feedback timeout Thanks Marc
Marc Perisa wrote: > Please close the PR due to feedback timeout > > Thanks > > Marc > > Sorry, I copied the wrong mail template ... The right one is: Please close this PR. It is better described at http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/24903 Thanks Marc
State Changed From-To: open->patched Modern GNU tar which was just imported into the -CURRENT doesn't have this problem. Therefore, the problem will befilly resolved when tar upgrade is MFC'ed in about 1 month.
State Changed From-To: patched->closed GNU tar 1.13.25 has been MFCed.