threads / discuss / 25209

git-svn error

Subject: git-svn error

## tl;dr

4 messages between Sep 23, 2010 and Sep 24, 2010.

replies: 3people: 2as markdown or json

Nate Parsons· Sep 23, 2010, 14:30 UTC · lore

Hi all,

I'm experiencing an error message importing a new svn repository using cygwin git, version 1.7.2.3

> fatal: refs/remotes/trunk: not a valid SHA1
> update-ref refs/heads/master refs/remotes/trunk: command returned error: 128

My .git/config file (nothing looks amiss to me):
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
	ignorecase = true
[svn-remote "svn"]
	url = <redacted>
	fetch = iem/procedures/iem:refs/remotes/trunk
	branches = iem/procedures/Z_Folders/*:refs/remotes/*

It appears that this error was seen before in an older version that didn't deal with extra "/"s appropriately, but I don't see that issue here.

Thanks, -Nate

Nate Parsons· Sep 23, 2010, 19:45 UTC · re: Nate Parsons · lore

Re: git-svn error

Hi all,

I reproduced the problem on openSUSE, running git 1.7.3. I can't provide access to the subversion repository, but I can do anything else to help diagnose the problem.

-Nate

On Thu, Sep 23, 2010 at 10:30 AM, Nate Parsons <parsons.nate@gmail.com> wrote:

Show 27 quoted lines

> Hi all,
>
> I'm experiencing an error message importing a new svn repository using
> cygwin git, version 1.7.2.3
>
>> fatal: refs/remotes/trunk: not a valid SHA1
>> update-ref refs/heads/master refs/remotes/trunk: command returned error: 128
>
> My .git/config file (nothing looks amiss to me):
> [core]
>        repositoryformatversion = 0
>        filemode = true
>        bare = false
>        logallrefupdates = true
>        ignorecase = true
> [svn-remote "svn"]
>        url = <redacted>
>        fetch = iem/procedures/iem:refs/remotes/trunk
>        branches = iem/procedures/Z_Folders/*:refs/remotes/*
>
> It appears that this error was seen before in an older version that
> didn't deal with extra "/"s appropriately, but I don't see that issue
> here.
>
> Thanks,
> -Nate
>

Michael J Gruber· Sep 24, 2010, 07:28 UTC · re: Nate Parsons · lore

Re: git-svn error

Nate Parsons venit, vidit, dixit 23.09.2010 21:45:

Show 5 quoted lines

> Hi all,
> 
> I reproduced the problem on openSUSE, running git 1.7.3. I can't
> provide access to the subversion repository, but I can do anything
> else to help diagnose the problem.

How about providing some context of that error message, i.e. a transaction log? Also: Is this from a fresh repo?

Michael

Nate Parsons· Sep 24, 2010, 20:33 UTC · re: Michael J Gruber · lore

Re: git-svn error

On Fri, Sep 24, 2010 at 3:28 AM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

Show 10 quoted lines

>
> Nate Parsons venit, vidit, dixit 23.09.2010 21:45:
> > Hi all,
> >
> > I reproduced the problem on openSUSE, running git 1.7.3. I can't
> > provide access to the subversion repository, but I can do anything
> > else to help diagnose the problem.
>
> How about providing some context of that error message, i.e. a
> transaction log? Also: Is this from a fresh repo?

I'd be glad to do this, as long as nobody can use these logs to recreate the contents of my repository. What commands do I run?

This is happening in a fresh repo, I do the 'git svn init' first, and then 'git svn fetch $head' (where $head is actually a number). This is to work around my other git issue that hasn't gotten a response.

I was able to fetch the entire repository using a combination of TortoiseGit (for the initial init and fetch, until it died with a file permissions error) and then fetch the rest of my history with msysgit, so this isn't a show-stopping issue for me.

-Nate