{"action":"created","issue":{"url":"https://api.github.com/repos/mafintosh/tar-fs/issues/21","labels_url":"https://api.github.com/repos/mafintosh/tar-fs/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/mafintosh/tar-fs/issues/21/comments","events_url":"https://api.github.com/repos/mafintosh/tar-fs/issues/21/events","html_url":"https://github.com/mafintosh/tar-fs/issues/21","id":101595709,"number":21,"title":"Malformed extended header: missing newline","user":{"login":"verchol","id":359038,"avatar_url":"https://avatars.githubusercontent.com/u/359038?v=3","gravatar_id":"","url":"https://api.github.com/users/verchol","html_url":"https://github.com/verchol","followers_url":"https://api.github.com/users/verchol/followers","following_url":"https://api.github.com/users/verchol/following{/other_user}","gists_url":"https://api.github.com/users/verchol/gists{/gist_id}","starred_url":"https://api.github.com/users/verchol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/verchol/subscriptions","organizations_url":"https://api.github.com/users/verchol/orgs","repos_url":"https://api.github.com/users/verchol/repos","events_url":"https://api.github.com/users/verchol/events{/privacy}","received_events_url":"https://api.github.com/users/verchol/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-08-18T07:58:40Z","updated_at":"2015-08-27T10:25:11Z","closed_at":null,"body":"Hi,\r\n\r\nwhen trying to open (with another tar utility, such as gnu tar or docker) very large (1 GB+) tar files generated with tar-fs, one gets errors such as:\r\n* Malformed extended header: missing newline\r\n* Untar re-exec error: archive/tar: invalid tar header: output: \r\n\r\nFYI"},"comment":{"url":"https://api.github.com/repos/mafintosh/tar-fs/issues/comments/135374115","html_url":"https://github.com/mafintosh/tar-fs/issues/21#issuecomment-135374115","issue_url":"https://api.github.com/repos/mafintosh/tar-fs/issues/21","id":135374115,"user":{"login":"christianhuening","id":738953,"avatar_url":"https://avatars.githubusercontent.com/u/738953?v=3","gravatar_id":"","url":"https://api.github.com/users/christianhuening","html_url":"https://github.com/christianhuening","followers_url":"https://api.github.com/users/christianhuening/followers","following_url":"https://api.github.com/users/christianhuening/following{/other_user}","gists_url":"https://api.github.com/users/christianhuening/gists{/gist_id}","starred_url":"https://api.github.com/users/christianhuening/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/christianhuening/subscriptions","organizations_url":"https://api.github.com/users/christianhuening/orgs","repos_url":"https://api.github.com/users/christianhuening/repos","events_url":"https://api.github.com/users/christianhuening/events{/privacy}","received_events_url":"https://api.github.com/users/christianhuening/received_events","type":"User","site_admin":false},"created_at":"2015-08-27T10:25:10Z","updated_at":"2015-08-27T10:25:10Z","body":"Yeah update here: The problem definitely is not related to the files I have in my archive. We now use a work-around which involves a system call to the underlying ubuntu's tar command. this is safe for now, since we're using a docker image an can rely on that. But it's not cool :("}}