git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
	Git Mailing List <git@vger.kernel.org>,
	Mihai Sucan <mihai.sucan@gmail.com>
Subject: Re: git svn errors out with git-cat-file "usage" message
Date: Thu, 30 Apr 2009 12:26:46 -0400	[thread overview]
Message-ID: <32541b130904300926x472d6d14p2896d3ade7566684@mail.gmail.com> (raw)
In-Reply-To: <46a038f90904300803h555f02b3n76d03c93d99f7506@mail.gmail.com>

On Thu, Apr 30, 2009 at 11:03 AM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
> On Thu, Apr 30, 2009 at 4:41 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
>> Try this:
>>
>>  strace -fF git svn  clone  -T trunk
>> http://paintweb.googlecode.com/svn paintweb.git 2>&1 | egrep -i
>> 'git.pm|git-svn'
>>
>> If you wade through the output, it should tell you which git.pm and
>> git-svn you're *really* getting.
>
> The output looks reasonable:
>
> $ strace -fF git svn  clone  -T trunk | http://paintweb.googlecode.com/svn paintweb.git 2>&1 | egrep -i 'git.pm|git-svn'
> execve("/home/martin/libexec/git-core/git-svn", ["git-svn", "clone",
> "-T", "trunk", "http://paintweb.googlecode.com/s"..., "paintweb.git"],
> [/* 44 vars */]) = 0
> open("/home/martin/libexec/git-core/git-svn", O_RDONLY|O_LARGEFILE) = 3
> stat64("/home/martin/share/perl/5.10.0/Git.pmc", 0xbffa451c) = -1
> ENOENT (No such file or directory)
> stat64("/home/martin/share/perl/5.10.0/Git.pm", {st_mode=S_IFREG|0444,
> st_size=35479, ...}) = 0
> open("/home/martin/share/perl/5.10.0/Git.pm", O_RDONLY|O_LARGEFILE) = 4
> [pid 23322] write(2, "Unexpected result returned from "...,
> 96Unexpected result returned from git cat-file at
> /home/martin/libexec/git-core/git-svn line 3252
> write(2, "Failed to read object 4b90eef952"..., 116Failed to read
> object 4b90eef95225bb9e34000e050d0cac8b84ab36f6 at
> /home/martin/libexec/git-core/git-svn line 3253.

And do the contents of these files match the ones in your git source
directory?  What are their md5sums?

/home/martin/libexec/git-core/git-svn
/home/martin/share/perl/5.10.0/Git.pm

Avery

  reply	other threads:[~2009-04-30 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 15:11 git svn errors out with git-cat-file "usage" message Martin Langhoff
2009-04-29 18:50 ` Avery Pennarun
2009-04-29 20:25   ` Michael J Gruber
2009-04-29 20:47     ` Martin Langhoff
2009-04-29 21:05       ` Michael J Gruber
2009-04-30  7:18         ` Martin Langhoff
2009-04-30  7:53           ` Michael J Gruber
2009-04-30  8:26           ` Andreas Ericsson
2009-04-30  8:46             ` Michael J Gruber
2009-04-30  8:53           ` Martin Langhoff
2009-04-30  9:28             ` Michael J Gruber
2009-04-30  9:42               ` Martin Langhoff
2009-04-30 14:41             ` Avery Pennarun
2009-04-30 15:03               ` Martin Langhoff
2009-04-30 16:26                 ` Avery Pennarun [this message]
2009-04-30 16:31                   ` Martin Langhoff
2009-04-30 16:49                     ` Michael J Gruber

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=32541b130904300926x472d6d14p2896d3ade7566684@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=mihai.sucan@gmail.com \
    /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).