You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Torsten Curdt (JIRA)" <ji...@apache.org> on 2010/12/15 11:37:01 UTC

[jira] Commented: (COMPRESS-124) Unable to extract a TAR file that contains sparse entries

    [ https://issues.apache.org/jira/browse/COMPRESS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971612#action_12971612 ] 

Torsten Curdt commented on COMPRESS-124:
----------------------------------------

Great contribution. Thanks.

For this to go into 1.2 (IMO) we will have to fix "reading an archive with sparse files and writing those files leads to invalid output files" first though.

> Unable to extract a TAR file that contains sparse entries
> ---------------------------------------------------------
>
>                 Key: COMPRESS-124
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-124
>             Project: Commons Compress
>          Issue Type: New Feature
>          Components: Archivers
>    Affects Versions: 1.1, 1.2
>         Environment: Platform independent. However, I'm currently using Window 7 Enterprise.
>            Reporter: Patrick Dreyer
>             Fix For: 1.2
>
>         Attachments: gnuSparseFile.patch
>
>
> Good news first: I already have the patch ready for that.
> I got several TAR files which I could not extract with any of the existing Java implementations, but I could extract all those TAR files successfully with GNU tar.
> It turned out that all the failing TAR files contained so called sparse files. Investigating the source code of all existing Java TAR implementations showed me that none of them even recognizes the existence of GNU sparse entries.
> Actually, I don't need to process one of the contained sparse files and I'm happy if I'm at least able to correctly untar all the non-sparsed files. Thus, it would be sufficient recognizing sparse files without the need to correctly un-sparse them while extracting. As long as all non-sparsed files get extracted correctly, I'm fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.