Re: git-svn is "Unable to determine upstream SVN information..."

From: Eric Wong <normalperson@yhbt.net>
Date: Jul 10, 2009, 20:33 UTC
Message-ID: <20090710203322.GA18051@dcvr.yhbt.net>
In-Reply-To: <5m5e55538tlnq40rup7rci61i2mg16q0dv@4ax.com>

Esben Skovenborg <esskov@oncable.dk> wrote:

Show 7 quoted lines

> On Thu, 9 Jul 2009 20:31:33 -0700, Eric Wong wrote:
> >Are there any weird characters in the URL?  
> 
> No. The only thing 'different' about this svn server is that it uses
> authentication (i.e. asks for name+password). But I suppose that when the
> git-svn fetch goes well, then this is not the problem?  Do the git-svn
> info and git-svn rebase even need to access the svn server?

Yes, rebase (without the -l) option needs it for sure. I think info can optionally use it, too. Does enabling authentication caching (enabled by default in SVN) help things? I haven't used the authentication prompt pieces in ages, they're hard to test in an automated fashion so they may have bit-rotted since I last looked at them...

Show 8 quoted lines

> >Off the top of my head I can't think of anything else; I assume
> >you're not allowed to share access to the repo (or to the clone) you're
> >having problems with?
> 
> Right, at least it's something we should talk about off-list.
> 
> Is there any way of asking git-svn *why* it is "unable to determine
> upstream SVN information from working tree history" ?

If you're comfortable with a little Perl, you can sprinkle some debug statements in working_head_info(). Feel free to email me directly offlist but my schedule looks pretty hectic today and this weekend and I may be offline a lot.

-- 
Eric Wong