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

Patrick Dreyer edited comment on COMPRESS-124 at 12/15/10 2:36 AM:
-------------------------------------------------------------------

Including not only the source but as well the documentation and changes.xml

Unfortunately, I was not able to generate a test TAR archive containing sparse 
files, even invoking GNU Tar with "--sparse" and all the TAR archives I have 
with such sparse files, contain information I'm not allowed disclose.
If someone is able to generate a TAR archive containing sparse files and 
provide such, pleas let me know so I can include the necessary unit tests.

      was (Author: patrickdreyer):
    Including not only the source but as well the documentation and changes.xml
  
> 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.

Reply via email to