From nobody  Sat Dec 13 12:21:46 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA12232;
          Sat, 13 Dec 1997 12:21:46 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199712132021.MAA12232@hub.freebsd.org>
Date: Sat, 13 Dec 1997 12:21:46 -0800 (PST)
From: giffunip@asme.org
To: freebsd-gnats-submit@freebsd.org
Subject: pkg_create uses an unstandard tar 
X-Send-Pr-Version: www-1.0

>Number:         5284
>Category:       bin
>Synopsis:       pkg_create uses an unstandard tar
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Dec 13 12:30:01 PST 1997
>Closed-Date:    Wed May 27 02:36:36 PDT 1998
>Last-Modified:  Sun Jul 25 18:30:25 GMT 2004
>Originator:     Pedro Giffuni S.
>Release:        Last checked on 2.2.1-Release
>Organization:
U. Nacional de Colombia
>Environment:
not relevant
>Description:
GNU tar claims not to be conforming to Posix 1003.1. In order to be
really portable the packaging tools should depend on a standards
compliant tar utility.
>How-To-Repeat:
The author of 'star' reports the following errors:
- Many bugs in implementation and design.
  (e.g. when handling/creating multi volume archives)
- The second logical EOF block in GNU-tar archives is missing with a 50%
  chance. This will cause correctly working tar implementations to 
  complain about an illegal/missing EOF in the tar archive.
- Deeply nested directory trees will not be dumped, Error message is:
  Too many open files
- Hard links with long names to files with long names do not work.
- GNU-tar cannot read Posix compliant tar archives with 
  long file names if the filename prefix it at least 138 characters.
  GNU-tar will think that it found an extended sparse GNU tar archive
  and get out of sync for the rest of the archive.


>Fix:
Perhaps pax(1) should be used as a replacement...I heard that BSDI 
replaces tar with pax.
>Release-Note:
>Audit-Trail:

From: Bruce Evans <bde@zeta.org.au>
To: freebsd-gnats-submit@FreeBSD.ORG, giffunip@asme.org
Cc:  Subject: Re: bin/5284: pkg_create uses an unstandard tar
Date: Sun, 14 Dec 1997 08:28:33 +1100

 >GNU tar claims not to be conforming to Posix 1003.1. In order to be
 >really portable the packaging tools should depend on a standards
 >compliant tar utility.
 
 cpio/README contains a one line patch for this (in GNU tar).  The patch
 is dated 1992.  It is not the default because it breaks tar's handling
 of long pathnames.
 
 >>Fix:
 >Perhaps pax(1) should be used as a replacement...I heard that BSDI 
 >replaces tar with pax.
 
 I trust GNU cpio more.
 
 Bruce
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Wed May 27 02:36:36 PDT 1998 
State-Changed-Why:  
As part of our PR auditing campaign, this PR has been closed due to it's 
age and lack of activity on the PR. 

There is a good chance that the problem reported have been solved 
as part of other activities. 

If this is not the case, please reopen this PR with fresh information 
on the manifestation of the bug. 

Sorry about the late reaction to this PR. 

From: Tim Kientzle <kientzle@freebsd.org>
To: freebsd-gnats-submit@freebsd.org, giffunip@asme.org
Cc:  
Subject: Re: bin/5284: pkg_create uses an unstandard tar
Date: Sun, 25 Jul 2004 11:25:24 -0700

 Reported in 1997, finally being fixed in 2004
 with the introduction of bsdtar as a replacement
 for gtar. ;-)
 
 FWIW, gtar 1.14 now supports --format=posix,
 which would also address this issue.
 
 Tim Kientzle
 
>Unformatted:
