Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 6 Oct 2015 03:26:26 +0000 (UTC)
From: "Stefan Bodewig (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12902302.1443950592000.32904.1444101986724@Atlassian.JIRA>
In-Reply-To: <JIRA.12902302.1443950592000@Atlassian.JIRA>
References: <JIRA.12902302.1443950592000@Atlassian.JIRA>
 <JIRA.12902302.1443950592095@arcas>
Subject: [jira] [Commented] (COMPRESS-324) Tar fails to detect fields for
 LF_GNUTYPE_LONGNAME archive
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefan Bodewig commented on COMPRESS-324:
-----------------------------------------

GNU tar itself uses {{LongLink}} both for long file names and long link names: http://git.savannah.gnu.org/cgit/tar.git/tree/src/create.c#n547

So your archive hasn't been created by GNU tar but likely by a different tool that tried to mimic the GNU long file name mode.

Anyway, GNU tar will happily extract the proper file name since - unlike Commons Compress - it only cares for the "linkType" flag and completely ignores the name of the tar entry.  We could and probably should do the same.

> Tar fails to detect fields for LF_GNUTYPE_LONGNAME archive
> ----------------------------------------------------------
>
>                 Key: COMPRESS-324
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-324
>             Project: Commons Compress
>          Issue Type: Bug
>            Reporter: MrBump
>         Attachments: java_apache_untar.zip
>
>
> Trying to extract a test tar archive with a simple java code. For a particular tar example fails to extract.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)