+++ This bug was initially created as a clone of Bug #239000 +++

Description of problem:

If pax attempts to create a ustar format archive with absolute path names it
fails on paths that are exactly 100 characters long. Where the length is <100 or
101-254 it works.

Version-Release number of selected component (if applicable):

pax-3.0-9

How reproducible:

always

Steps to Reproduce:
1. unpack the attached tar with    tar -x -C / -f pax_abs_test.tar
2. pax -w -f /var/tmp/px.tar /var/tmp/pax_abs_test -x ustar
3.
  
Actual results:
pax: File name too long for ustar
/var/tmp/pax_abs_test/this_file_fails_because_the_absolute_filename_is_exactly__100__characters_long


Expected results:

no errors, complete tar.

Additional info:

The pax source contains a specific mention of the boundary condition where the
name is of the form /str and 100 characters long and errs on the side of
absolute posix adherence. What it fails to account for is when the name is of
the form /dir/str and the length is 100 characters. In this situation it would
be valid to perform the normal split procedure as long as the split is not at
the first character.

--- Additional comment from mpoole on 2007-05-04 08:21:07 EDT ---

Created an attachment (id=154110)
tar file with absolute names of varying lengths to illustrate problem/test solution.

--- Additional comment from mpoole on 2007-05-04 08:23:21 EDT ---

Created an attachment (id=154111)
patch to fix absolute 100 char file issue

--- Additional comment from pm-rhel on 2008-02-01 14:08:29 EST ---

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

--- Additional comment from tao on 2008-03-03 07:11:25 EST ---

There have been no updates to this issue in the past 28 days. This issue
will now be closed due to inactivity. If this is in error, please reopen
the issue and check to make sure that it is current and in the proper
status. If the issue is something which is on a longer timeline than a
month, please change the status to one of the long term selections to
avoid closure due to inactivity.
This event sent from IssueTracker by AutoCloser  [Production Support
(Pune)]
 issue 116058

--- Additional comment from tao on 2010-02-26 09:55:45 EST ---

Event posted on 02-26-2010 09:55am EST by jkalliya

Closing the case.

Internal Status set to 'Resolved'
Status set to: Closed by Tech
Resolution set to: 'Closed by Client'

This event sent from IssueTracker by jkalliya 
 issue 116058