<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>37132</bug_id>
          
          <creation_ts>2004-01-03 12:05 0000</creation_ts>
          <short_desc>New tar fails to unpack certain archives properly</short_desc>
          <delta_ts>2004-01-19 21:25:28 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Unspecified</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>aliz@gentoo.org</reporter>
          <assigned_to>base-system@gentoo.org</assigned_to>
          <cc>043936y@acadiau.ca</cc>
    
    <cc>avenj@gentoo.org</cc>
    
    <cc>benoit.boissinot@ens-lyon.fr</cc>
    
    <cc>bla@af.gliwice.pl</cc>
    
    <cc>carpaski@gentoo.org</cc>
    
    <cc>chainsaw@gentoo.org</cc>
    
    <cc>chriskds25@yahoo.com</cc>
    
    <cc>derk@zapville.org</cc>
    
    <cc>ehmsen@gentoo.org</cc>
    
    <cc>gentoo@valli.org</cc>
    
    <cc>jochen.eisinger@gmx.de</cc>
    
    <cc>mallchin@blueyonder.co.uk</cc>
    
    <cc>mkennedy@gentoo.org</cc>
    
    <cc>president@sheergenius.com</cc>
    
    <cc>sgtphou@fire-eyes.org</cc>
    
    <cc>suka@gentoo.org</cc>
    
    <cc>tove@gentoo.org</cc>
    
    <cc>ykar@list.ru</cc>

      

      
          <long_desc isprivate="0">
            <who>aliz@gentoo.org</who>
            <bug_when>2004-01-03 12:05:07 0000</bug_when>
            <thetext>Some tar archives has paths like these in them: ..././...
when trying to unpack these archives with tar 1.13.92 it gives the following warning: tar: Removing leading ...

Confirmed tarballs that suffers from this are: libpcap-0.8.1, tcpdump-3.8.1 and iptables-1.2.9</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:10:47 0000</bug_when>
            <thetext>The tar problem manifests itself like this:

&gt;&gt;&gt; md5 src_uri ;-) tcpdump-3.8.1.tar.gz
&gt;&gt;&gt; Unpacking source...
&gt;&gt;&gt; Unpacking tcpdump-3.8.1.tar.gz to /var/tmp/portage/tcpdump-3.8.1/work
tar: Removing leading `tcpdump-3.8.1/./&apos; from member names
&gt;&gt;&gt; Source unpacked.

!!! ERROR: net-analyzer/tcpdump-3.8.1 failed.
!!! Function econf, Line 341, Exitcode 1
!!! no configure script found

And those weird paths are actually in the mentioned tar&apos;s:
tcpdump-3.8.1/./
tcpdump-3.8.1/./lbl/
tcpdump-3.8.1/./lbl/os-osf4.h
(truncated)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>aliz@gentoo.org</who>
            <bug_when>2004-01-03 12:13:21 0000</bug_when>
            <thetext>The result is that tar strips out the subdir in the tarball unpacking it directly to $PORTAGE_TMDIR/work and not $PORTAGE_TMPDIR/work/libpcap-0.8.1</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:21:00 0000</bug_when>
            <thetext>A fragment from tar-1.13.92/ChangeLog
One entry seems relevant, marked with &lt;!&gt;

003-11-14  Sergey Poznyakoff  &lt;gray@Mirddin.farlep.net&gt;

        * src/tar.h (archive_format): USTAR_FORMAT: New type.
        * src/create.c: Added POSIX.1-1988 support.
    &lt;!&gt;* src/names.c (safer_name_suffix): Skip leading ./
        * src/tar.c: New option --format=ustar forces
        POSIX.1-1988 archive format.
        * tests/delete03.sh: Updated.
        * tests/extrac04.sh: Updated.
        * tests/multiv01.sh: Updated.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:34:48 0000</bug_when>
            <thetext>Looks as if the &quot;P&quot; option to tar (--absolute-names) disables the check.
Playing around with this.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:40:33 0000</bug_when>
            <thetext>Created an attachment (id=23085)
ebuild.sh.diff

This adds --absolute-names to the unpack command in ebuild.sh and allows me to
install libpcap.
Please perform a sanity check on this and treat it with care until I&apos;ve tested
more thoroughly.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-03 12:42:11 0000</bug_when>
            <thetext>i dont really think the way to go is patching ebuild.sh

it&apos;s obvious it&apos;s a bug in tar, fix tar and we dont have to screw around with releasing another portage</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:45:56 0000</bug_when>
            <thetext>Tested with:  libpcap-0.8.1, tcpdump-3.8.1 and iptables-1.2.9
These weren&apos;t willing to install earlier and work now.

Tested with: kdegames-3.2.0_beta2, tar-1.13.92 and portage-2.0.49-r20
These worked before, and still work now.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 12:47:02 0000</bug_when>
            <thetext>I&apos;m not a C coder though.

Could mask the tar version, file a bug upstream or have someone else hack on names.c, I guess.

Anyway, should anyone be willing to take this route, it will work.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 13:14:27 0000</bug_when>
            <thetext>Created an attachment (id=23092)
1.13.92-disable-dotslash-check.diff

This hardcodes the (apparently buggy) check to disabled in the tar sources.
Basically, this is the same solution as provided earlier, but then in a way
that doesn&apos;t require a portage upgrade (which would be tedious indeed, SpanKY,
agreed).</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 13:15:20 0000</bug_when>
            <thetext>Created an attachment (id=23093)
tar-1.13.92.ebuild.diff

And ofcourse the diff to the tar ebuild to apply this diff.

How&apos;s this? (Tested again, same 6 packages)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-03 13:50:55 0000</bug_when>
            <thetext>absolute_names_option is referenced in both src/extract.c and src/names.c, so perhaps the better way of doing it is to patch src/tar.c around line 1246 with absolute_names_option = true;</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 13:58:43 0000</bug_when>
            <thetext>Created an attachment (id=23099)
1.13.92-hardcode-absolute-names-to-on.diff

Redoing things the hardcoded way, in tar.c, as asked.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-03 13:59:37 0000</bug_when>
            <thetext>Created an attachment (id=23100)
tar-1.13.92.ebuild.diff

And the ebuild change to have the patch applied.

Bugfixes to order, anyone else that would like a change? :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-03 21:54:31 0000</bug_when>
            <thetext>*** Bug 37157 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>aliz@gentoo.org</who>
            <bug_when>2004-01-04 02:52:35 0000</bug_when>
            <thetext>*** Bug 37170 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>aliz@gentoo.org</who>
            <bug_when>2004-01-04 03:58:59 0000</bug_when>
            <thetext>*** Bug 36810 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>aliz@gentoo.org</who>
            <bug_when>2004-01-04 04:00:03 0000</bug_when>
            <thetext>*** Bug 37103 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jochen.eisinger@gmx.de</who>
            <bug_when>2004-01-04 04:55:38 0000</bug_when>
            <thetext>*** Bug 37176 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>kloeri@gentoo.org</who>
            <bug_when>2004-01-04 06:41:14 0000</bug_when>
            <thetext>*** Bug 37190 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>tseng@gentoo.org</who>
            <bug_when>2004-01-04 08:06:09 0000</bug_when>
            <thetext>*** Bug 37195 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2004-01-04 08:54:58 0000</bug_when>
            <thetext>thanks for the patch, Tony, added to portage and reporting this issue upstream</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2004-01-04 09:16:32 0000</bug_when>
            <thetext>*** Bug 37202 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2004-01-04 09:26:15 0000</bug_when>
            <thetext>*** Bug 37203 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2004-01-05 04:29:03 0000</bug_when>
            <thetext>*** Bug 37287 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>corporate_gadfly@hotmail.com</who>
            <bug_when>2004-01-05 11:05:11 0000</bug_when>
            <thetext>For the slow people among us (who need everything spelled out), the fix is to:
a) emerge tar, and then
b) emerge libpcap.
tar version app-arch/tar-1.13.92-r1 seems to address the problem mentioned here.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-06 10:53:46 0000</bug_when>
            <thetext>I do not think this is the proper fix ..
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-06 10:58:45 0000</bug_when>
            <thetext>Created an attachment (id=23245)
tar-1.13.92-fix-pathstrip.patch

The problem is the strip code also strip &apos;./&apos;, and not just &apos;../&apos;.  I do not
see why the code also strip &apos;./&apos;, as it refers to the current dir (or the
proper file if you append the path given to -C arg), and as we all know, RH
etc starts to ship tarballs that have pathnames start with &apos;./&apos; for security
reasons - same reason why unzip add &apos;./&apos; to all paths.

Anyhow, attached is patch that fixes the code not to stip &apos;./&apos;.

Comments?
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-06 11:05:36 0000</bug_when>
            <thetext>On another matter - if you look at the following code:

--
          if (p[0] == &apos;.&apos;)
            {
              if (p[1] == &apos;.&apos; &amp;&amp; (ISSLASH (p[2]) || !p[2]))
                prefix_len = p + 2 - file_name;
              else if (ISSLASH (p[1]))
                prefix_len = p + 1 - file_name;
            }
--

from src/names.c (&apos;safer_name_suffix&apos; function), is it safe?  I see no
test to see if the lenght of the input filename is &gt;= 3 chars, but still
the code checks p[0], p[1] and p[2] without checking if its valid (sure,
there is the &apos;!p[2]&apos; check, but that follows &apos;ISSLASH (p[2])&apos;).  My C
is a bit rustic, so I might see something where there is none ...
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lu_zero@gentoo.org</who>
            <bug_when>2004-01-06 11:25:16 0000</bug_when>
            <thetext>if the string is 0 terminated should not be a problem:

if p[1] == 0 it exits and won&apos;t check the other conditions.

Maybe I forgot something, from a quick look at the rest of the code it should not cause any harm.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-06 11:39:49 0000</bug_when>
            <thetext>If p[2] is out of bounds, the &apos;ISSLASH (p[2])&apos; will touch it.  The p==0 test
is only after, and this is not part of that while loop ...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-06 14:04:12 0000</bug_when>
            <thetext>Ok, here is the proper fix:

http://savannah.gnu.org/cgi-bin/viewcvs/tar/tar/src/names.c.diff?r1=1.36&amp;r2=1.37&amp;diff_format=u

I missed a change it seems :)  I&apos;ll commit tonight if somebody do not get there
before me.

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rjtupas@mac.com</who>
            <bug_when>2004-01-07 02:21:03 0000</bug_when>
            <thetext>I suffered from the exact same problem. After upgrading app-arch/tar-1.13.92 to 1.13.92-r1, I was able to successfully upgrade libpcap and iptables.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-07 22:17:51 0000</bug_when>
            <thetext>*** Bug 37352 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chainsaw@gentoo.org</who>
            <bug_when>2004-01-07 23:06:05 0000</bug_when>
            <thetext>(From update of attachment 23099)
This workaround is no longer necessary now that the true cause is found.
Obsoleting.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-08 17:17:27 0000</bug_when>
            <thetext>*** Bug 37610 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>suka@gentoo.org</who>
            <bug_when>2004-01-10 04:47:41 0000</bug_when>
            <thetext>http://bugs.gentoo.org/show_bug.cgi?id=37728

Seems to be a duplicate of this one too, openoffice and openoffice-ximian both break with the current unstable app-arch/tar-1.13.92-r1</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-11 06:02:17 0000</bug_when>
            <thetext>Added -r2 with new patch - can we verify that it still works?

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2004-01-11 08:12:14 0000</bug_when>
            <thetext>Ok, seems this also fixes the openoffice issues with -r1 (bug #37610).
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-01-19 21:25:28 0000</bug_when>
            <thetext>*** Bug 38739 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
      
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23085</attachid>
            <date>2004-01-03 12:40 0000</date>
            <desc>ebuild.sh.diff</desc>
            <filename>ebuild.sh.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIC91c3IvbGliL3BvcnRhZ2UvYmluL2VidWlsZC5zaC5vcmlnCTIwMDQtMDEtMDMgMjE6MzY6
MjUuMDMwOTU4NTQ0ICswMTAwCisrKyAvdXNyL2xpYi9wb3J0YWdlL2Jpbi9lYnVpbGQuc2gJMjAw
NC0wMS0wMyAyMTozNzoyNS45MjA3MDE4OTYgKzAxMDAKQEAgLTI4MCw3ICsyODAsNyBAQAogCWlm
IFsgIiRVU0VSTEFORCIgPT0gIkJTRCIgXTsgdGhlbgogCQl0YXJ2YXJzPSIiCiAJZWxzZQotCQl0
YXJ2YXJzPSItLW5vLXNhbWUtb3duZXIiCQorCQl0YXJ2YXJzPSItLW5vLXNhbWUtb3duZXIgLS1h
YnNvbHV0ZS1uYW1lcyIJCiAJZmkJCiAKIAlmb3IgeCBpbiAiJEAiOyBkbwo=
</data>        

          </attachment>
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23092</attachid>
            <date>2004-01-03 13:14 0000</date>
            <desc>1.13.92-disable-dotslash-check.diff</desc>
            <filename>1.13.92-disable-dotslash-check.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIHNyYy9uYW1lcy5jLm9yaWcJMjAwNC0wMS0wMyAyMjowNDo1My44NTExNzgzODQgKzAxMDAK
KysrIHNyYy9uYW1lcy5jCTIwMDQtMDEtMDMgMjI6MDY6MDEuNzcyODUyNzIwICswMTAwCkBAIC0x
MDEwLDcgKzEwMTAsNyBAQAogewogICBjaGFyIGNvbnN0ICpwOwogCi0gIGlmIChhYnNvbHV0ZV9u
YW1lc19vcHRpb24pCisgIGlmICgxKSAvKiBUaGlzIGRpc2FibGVzIGEgYnVnZ3kgY2hlY2sgb24g
Li8gaW4gcGF0aG5hbWVzICovCiAgICAgcCA9IGZpbGVfbmFtZTsKICAgZWxzZQogICAgIHsK
</data>        

          </attachment>
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23093</attachid>
            <date>2004-01-03 13:15 0000</date>
            <desc>tar-1.13.92.ebuild.diff</desc>
            <filename>tar-1.13.92.ebuild.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIC91c3IvcG9ydGFnZS9hcHAtYXJjaC90YXIvdGFyLTEuMTMuOTIuZWJ1aWxkCTIwMDMtMTIt
MjkgMDU6MDI6MjYuMDAwMDAwMDAwICswMTAwCisrKyB0YXItMS4xMy45Mi5lYnVpbGQJMjAwNC0w
MS0wMyAyMjowOTowMS40NDE4MDUxMzYgKzAxMDAKQEAgLTI2LDYgKzI2LDggQEAKIAkjIEZpeCBj
b25maWd1cmUgc2NyaXB0cyB0byBzdXBwb3J0IGxpbnV4LW1pcHMgdGFyZ2V0cwogCWdudWNvbmZp
Z191cGRhdGUKIAorCWVwYXRjaCAke0ZJTEVTRElSfS8ke1BWfS1kaXNhYmxlLWRvdHNsYXNoLWNo
ZWNrLmRpZmYKKwogCWVjb25mIFwKIAkJLS1iaW5kaXI9L2JpbiBcCiAJCS0tbGliZXhlY2Rpcj0v
dXNyL2xpYi9taXNjIFwK
</data>        

          </attachment>
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23099</attachid>
            <date>2004-01-03 13:58 0000</date>
            <desc>1.13.92-hardcode-absolute-names-to-on.diff</desc>
            <filename>1.13.92-hardcode-absolute-names-to-on.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIHNyYy90YXIuYy5vcmlnCTIwMDMtMTItMDEgMTU6MTE6MDUuMDAwMDAwMDAwICswMTAwCisr
KyBzcmMvdGFyLmMJMjAwNC0wMS0wMyAyMjo1Mzo0Ny40MDMyMTA2ODggKzAxMDAKQEAgLTEyNDQs
NiArMTI0NCwxMCBAQAogCX0KICAgICB9CiAKKyAgLyogSGFyZGNvZGUgYWJzb2x1dGVfbmFtZXNf
b3B0aW9uIHRvIGVuYWJsZWQsIHRvIGF2b2lkIGdldHRpbmcgYml0dGVuCisgICAgIGJ5IGEgYnVn
Z3kgY2hlY2sgdGhhdCByZW1vdmVzIHRvbyBtdWNoIHdoZW4gLi8gaXMgaW4gdGhlIHBhdGggKi8K
KyAgYWJzb2x1dGVfbmFtZXNfb3B0aW9uID0gdHJ1ZTsKKwogICAvKiBIYW5kbGUgb3BlcmFuZHMg
YWZ0ZXIgYW55ICItLSIgYXJndW1lbnQuICAqLwogICBmb3IgKDsgb3B0aW5kIDwgYXJnYzsgb3B0
aW5kKyspCiAgICAgewo=
</data>        

          </attachment>
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23100</attachid>
            <date>2004-01-03 13:59 0000</date>
            <desc>tar-1.13.92.ebuild.diff</desc>
            <filename>tar-1.13.92.ebuild.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIC91c3IvcG9ydGFnZS9hcHAtYXJjaC90YXIvdGFyLTEuMTMuOTIuZWJ1aWxkCTIwMDMtMTIt
MjkgMDU6MDI6MjYuMDAwMDAwMDAwICswMTAwCisrKyAvdXNyL2xvY2FsL3BvcnRhZ2UvYXBwLWFy
Y2gvdGFyL3Rhci0xLjEzLjkyLmVidWlsZAkyMDA0LTAxLTAzIDIyOjU1OjIxLjY4MjE0NDM2MCAr
MDEwMApAQCAtMjYsNiArMjYsOCBAQAogCSMgRml4IGNvbmZpZ3VyZSBzY3JpcHRzIHRvIHN1cHBv
cnQgbGludXgtbWlwcyB0YXJnZXRzCiAJZ251Y29uZmlnX3VwZGF0ZQogCisJZXBhdGNoICR7RklM
RVNESVJ9LyR7UFZ9LWhhcmRjb2RlLWFic29sdXRlLW5hbWVzLXRvLW9uLmRpZmYKKwogCWVjb25m
IFwKIAkJLS1iaW5kaXI9L2JpbiBcCiAJCS0tbGliZXhlY2Rpcj0vdXNyL2xpYi9taXNjIFwK
</data>        

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>23245</attachid>
            <date>2004-01-06 10:58 0000</date>
            <desc>tar-1.13.92-fix-pathstrip.patch</desc>
            <filename>tar-1.13.92-fix-pathstrip.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIHRhci0xLjEzLjkyL3NyYy9uYW1lcy5jLm9yaWcJMjAwNC0wMS0wNiAyMDo0NTo1NC4zMDYx
MjAyMDAgKzAyMDAKKysrIHRhci0xLjEzLjkyL3NyYy9uYW1lcy5jCTIwMDQtMDEtMDYgMjA6NDY6
MDcuNjQxMDkyOTc2ICswMjAwCkBAIC0xMDI1LDggKzEwMjUsMTAgQEAKIAkgICAgewogCSAgICAg
IGlmIChwWzFdID09ICcuJyAmJiAoSVNTTEFTSCAocFsyXSkgfHwgIXBbMl0pKQogCQlwcmVmaXhf
bGVuID0gcCArIDIgLSBmaWxlX25hbWU7CisjaWYgMAogCSAgICAgIGVsc2UgaWYgKElTU0xBU0gg
KHBbMV0pKQogCQlwcmVmaXhfbGVuID0gcCArIDEgLSBmaWxlX25hbWU7CisjZW5kaWYKIAkgICAg
fQogCSAgCiAJICBkbwo=
</data>        

          </attachment>
    </bug>

</bugzilla>