git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
	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 10:53:08 +0200	[thread overview]
Message-ID: <46a038f90904300153v22aa3e9fo407ff5084b58b5fc@mail.gmail.com> (raw)
In-Reply-To: <46a038f90904300018u7101943blef084dc907a04c8d@mail.gmail.com>

On Thu, Apr 30, 2009 at 9:18 AM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
> Bingo! Yes,
>
> ~$ which git-cat-file
> /usr/bin/git-cat-file
> ~$ /usr/bin/git version
> git version 1.5.6.3

Actually, after removing the git-core package and all its dependencies...

# same git version that succeeds on Fedora 9, here says:
$ git svn  clone  -T trunk  http://paintweb.googlecode.com/svn paintweb.git
usage: git-cat-file [-t|-s|-e|-p|<type>] <sha1>
error closing pipe: Broken pipe at
/home/martin/libexec/git-core/git-svn line 3252
cat-file --batch: command returned error: 129

error closing pipe: Bad file descriptor at
/home/martin/libexec/git-core/git-svn line 0
error closing pipe: Bad file descriptor at
/home/martin/libexec/git-core/git-svn line 0
$ git version
git version 1.6.0.6

# a newer git says...
$ git svn clone -T trunk --ignore-paths releases
http://paintweb.googlecode.com/svn paintweb.git
usage: git-cat-file [-t|-s|-e|-p|<type>] <sha1>
Unexpected result returned from git cat-file at
/home/martin/libexec/git-core/git-svn line 3526
Failed to read object 4b90eef95225bb9e34000e050d0cac8b84ab36f6 at
/home/martin/libexec/git-core/git-svn line 3527.

$ git version
git version 1.6.2.4.10.g2254d

... the plot thickens...

There is nothing in my env that would confuse git -- and my PATH has
~/bin as the first entry, trumping everything else. So perhaps the
debian package had nothing to do with this?

Perl SVN bindings? How do I debug that side of things?

cheers,



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

  parent reply	other threads:[~2009-04-30  8:53 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 [this message]
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
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=46a038f90904300153v22aa3e9fo407ff5084b58b5fc@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --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).