commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Dreyer (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-124) Unable to extract a TAR file that contains sparse entries
Date Wed, 27 Jul 2011 06:03:09 GMT


Patrick Dreyer commented on COMPRESS-124:

I absolutely agree with overwriting {{canReadEntryData()}} instead having {{isGNUSparse()}}.

Looking at the commits, we still have no unit tests, right?
And, Stefan, you mentioned the commit of a tar archive using the oldgnu format, but where
is it?

> Unable to extract a TAR file that contains sparse entries
> ---------------------------------------------------------
>                 Key: COMPRESS-124
>                 URL:
>             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
>         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.
> The TAR files in question have all been VMware Diagnostic File bundles.
> See
to know how to get them.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message