[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-449) TarGzExporter wrong packing of paths with more than 100 characters

Michal Matloka (JIRA) jira-events at lists.jboss.org
Wed Apr 10 17:22:55 EDT 2013


    [ https://issues.jboss.org/browse/SHRINKWRAP-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766304#comment-12766304 ] 

Michal Matloka commented on SHRINKWRAP-449:
-------------------------------------------

http://www.delorie.com/gnu/docs/tar/tar_114.html

{quote}
GNU tar was based on an early draft of the POSIX 1003.1 ustar standard. GNU extensions to tar, such as the support for file names longer than 100 characters, use portions of the tar header record which were specified in that POSIX draft as unused. Subsequent changes in POSIX have allocated the same parts of the header record for other purposes. As a result, *GNU tar is incompatible with the current POSIX spec, and with tar programs that follow it*.
{quote}
                
> TarGzExporter wrong packing of paths with more than 100 characters
> ------------------------------------------------------------------
>
>                 Key: SHRINKWRAP-449
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-449
>             Project: ShrinkWrap
>          Issue Type: Bug
>          Components: impl-base
>            Reporter: Matej Lazar
>            Assignee: Michal Matloka
>
> Prefixes of long paths (> 100 chars) are ignored when unpacking archives with tar on linux.
> Packing "moreThan100/long/path/to/file.class" with TarGzExporter, is unpacked by linux tar as "long/path/to/file.class". 
> Where "long/path/to/file.class" is just bellow 100 chars.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the shrinkwrap-issues mailing list