[issue14810] Bug in tarfile

David Ibarra added the comment: I too cannot reproduce this, tarfile seems to recognizes that it isn't a valid tar file (tested on OS X): Davids-MacBook-Air:Workspace dibarra$ ls -l total 8 -rw-r--r-- 1 dibarra staff 0 May 30 1956 testfile Davids-MacBook-Air:Workspace dibarra$ tar -cvf

[issue14810] Bug in tarfile

Changes by Lars Gustäbel : -- assignee: -> lars.gustaebel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue14810] Bug in tarfile

Hans Werner May added the comment: "Out of curiosity: where did you get a file that was last modified in 1956?" No idea, this was a jpeg file, probably downloaded from internet. Btw, on Linux you can manipulate the creation date with the touch command, so it is possible to create a tarball wi

[issue14810] Bug in tarfile

Lars Gustäbel added the comment: This issue is related to issue13158 which deals with a GNU tar specific extension to the original tar format. In that issue a negative number in the uid/gid fields caused problems. In your case the problem is a negative mtime field. Reading these particular n

[issue14810] Bug in tarfile

Martin v. Löwis added the comment: The tar file format does nt support timestamps before 1970. From http://sunsite.ualberta.ca/Documentation/Gnu/tar-1.13/html_chapter/tar_8.html "POSIX tar format can represent time stamps in the range 1970-01-01 00:00:00 through 2242-03-16 12:56:31 UTC." ...

[issue14810] Bug in tarfile

New submission from Hans Werner May : Bug in tarfile: In extractall, when a file exists in tarball with changetime older than (I don't know, in my case it was year 1956) tarfile raises an Overflow exception: File "/usr/lib64/python2.7/tarfile.py", line 2298, in utime os.utime(targetpath,