git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russ Dill" <russ.dill@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: git-svn+cygwin failed fetch
Date: Thu, 12 Jul 2007 10:49:22 -0700	[thread overview]
Message-ID: <f9d2a5e10707121049o758109c0l4ebeb08250093ba0@mail.gmail.com> (raw)
In-Reply-To: <20070712054800.GC29676@muzzle>

On 7/11/07, Eric Wong <normalperson@yhbt.net> wrote:
> Russ Dill <russ.dill@gmail.com> wrote:
> > On 7/11/07, Eric Wong <normalperson@yhbt.net> wrote:
> > >Russ Dill <russ.dill@gmail.com> wrote:
> > >> [...]/src $ mkdir foo
> > >> [...]/src $ cd foo
> > >> [...]/src/foo $ git-svn init -t tags -b branches -T trunk
> > >> https://www.[...].com/svn/foo/bar/bla
> > >> Initialized empty Git repository in .git/
> > >> Using higher level of URL: https://www.[...].com/svn/foo/bar/bla =>
> > >> https://www.[...].com/svn/foo
> > >>
> > >> [...]/src/foo $ git-svn fetch
> > >> config --get svn-remote.svn.url: command returned error: 1
> > >>
> > >> [...]/src/foo $ git config --get svn-remote.svn.url
> > >> https://www.[...].com/svn/foo
> > >
> > >Sorry, I can't help here other than recommending a real UNIX with
> > >fork + pipe + exec and all that fun stuff.
> > >
> > >git-svn relies heavily[1] on both input and output pipes of the
> > >safer-but-made-for-UNIX fork + pipe + exec(@list) variety, so I suspect
> > >this is just the tip of the iceberg for Windows incompatibilies with
> > >git-svn...
> >
> > Its actually reading and writing quite a bit of stuff from the config
> > file, so why this one simple command would fail eludes me. Especially
> > since it wrote it there in the first place. If I comment out the
> > command_oneline and hardcode the value I know it should return,
> > git-fetch runs. Its actually been running for several hours now.
>
> Wow.  That's a pleasant surprise that anything in git-svn works at all
> on cygwin.  I was almost certain git-svn on Windows was a hopeless cause
> from other chatter I had heard on the mailing list.
>
> command_oneline() is used everywhere in that code, so I'm at a total loss
> as to why it would fail in one place.  Can you put a the following lines
> right before where it was failing?
>
>         print "GIT_CONFIG: $ENV{GIT_CONFIG} | GIT_DIR: $ENV{GIT_DIR}\n";
>         system('cat', "$ENV{GIT_DIR}/config");
>
> And tell me what it outputs?


Use of uninitialized value in concatenation (.) or string at
/usr/bin/git-svn line 1189.
GIT_CONFIG:  | GIT_DIR: .git
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[svn-remote "svn"]
        url = https://www.[...].com/svn/foo
        fetch = bar/bla/trunk:refs/remotes/trunk
        branches = bar/bla/branches/*:refs/remotes/*
        tags = bar/bla/tags/*:refs/remotes/tags/*
[gui]
        geometry = 864x678+162+162 104 204


If I export GIT_CONFIG, then the problem goes away. Much better work
around then hardcoding svn-remote.svn.url

The git-svn fetch died overnight due to an http error. Its restarted
now. There are dozens of branches and tags in the repo, and each one
seems to take about a half hour to and hour to fully fetch. It takes a
similar amount of time to checkout trunk with tortise SVN. The repo is
local, but I don't have direct access to it.

  reply	other threads:[~2007-07-12 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 18:06 git-svn+cygwin failed fetch Russ Dill
2007-07-11  9:06 ` Eric Wong
2007-07-11  9:54   ` Russ Dill
2007-07-12  5:48     ` Eric Wong
2007-07-12 17:49       ` Russ Dill [this message]
2007-07-12 18:27         ` Eric Wong

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=f9d2a5e10707121049o758109c0l4ebeb08250093ba0@mail.gmail.com \
    --to=russ.dill@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /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).