git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-tar-tree: add a test case (resent)
Date: Fri, 03 Jun 2005 16:43:34 +0200	[thread overview]
Message-ID: <42A06C96.8050107@lsrfire.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.58.0506030728120.1876@ppc970.osdl.org>

Linus Torvalds schrieb:
> 	torvalds@ppc970:~> tar --version
> 	tar (GNU tar) 1.13.25
> 	Copyright © 2001 Free Software Foundation, Inc.
> 	This program comes with NO WARRANTY, to the extent permitted by law.
> 	You may redistribute it under the terms of the GNU General Public License;
> 	see the file named COPYING for details.
> 	Written by John Gilmore and Jay Fenlason.

[...]

> I get
> 
> 	?rw------- git/git          52 1969-12-31 16:00:00 pax_global_header unknown file type `g'
> 	drwxr-xr-x git/git           0 2005-05-27 15:00:00 a/
> 	-rw-r--r-- git/git          18 2005-05-27 15:00:00 a/1.......10........20........30........40......481.......10........20........30........40........50
> 	?rw------- git/git         111 2005-05-27 15:00:00 37e07bc886b166ad2525f1cc7a2df9bda0e07a02.paxheader unknown file type `x'
> 	-rw-r--r-- git/git          18 2005-05-27 15:00:00 37e07bc886b166ad2525f1cc7a2df9bda0e07a02.data
> 	?rw------- git/git         112 2005-05-27 15:00:00 f72c8a14fa272506e5de2d779cfe088769158b61.paxheader unknown file type `x'
> 	-rw-r--r-- git/git          18 2005-05-27 15:00:00 f72c8a14fa272506e5de2d779cfe088769158b61.data
> 	?rw------- git/git         113 2005-05-27 15:00:00 b53ac87f1a63ea1a2eec65cc8b5bed9130b8c114.paxheader unknown file type `x'
> 	-rw-r--r-- git/git          18 2005-05-27 15:00:00 b53ac87f1a63ea1a2eec65cc8b5bed9130b8c114.data
> 	-rw-r--r-- git/git          16 2005-05-27 15:00:00 a/a
> 	drwxr-xr-x git/git           0 2005-05-27 15:00:00 a/bin/
> 	-rwxr-xr-x git/git      719924 2005-05-27 15:00:00 a/bin/sh
> 	tar: Unexpected EOF in archive
> 	tar: Error is not recoverable: exiting now
> 
> which doesn't tell me anything, except I assume it means that my tar 
> doesn't understand extended headers.

That's true, but you don't need them if all your pathes' lengths are 100
or shorter.  Of course the test exercising long paths will always fail
with your version of tar.  I should split it out better, so you will at
least get a positive result for short paths.  I just didn't expect such
an old version of tar to be in use anymore. :-P

But your output shows a more serious problem: "Unexpected EOF" means the
archive is missing a piece.  I sent you a patch for that bug in my
previous mail.

Thanks,
Rene

  reply	other threads:[~2005-06-03 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 18:50 [PATCH] git-tar-tree: add a test case (resent) Rene Scharfe
2005-06-02 20:05 ` Junio C Hamano
2005-06-02 20:50   ` Rene Scharfe
2005-06-03  1:34 ` Linus Torvalds
2005-06-03  5:34   ` Rene Scharfe
2005-06-03 14:31     ` Linus Torvalds
2005-06-03 14:43       ` Rene Scharfe [this message]
2005-06-03 11:25   ` Rene Scharfe
2005-06-03 14:46     ` Linus Torvalds
2005-06-03 14:51       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42A06C96.8050107@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).