{"thread":{"id":"25209","subject":"git-svn error","startedAt":"2010-09-23T14:30:22Z","lastAt":"2010-09-24T20:33:36Z","messageCount":4,"participants":["Nate Parsons","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"151361","messageId":"AANLkTi=5ficziLK8cfikotoxkgUDLfhAM_RLzCOcOv5U@mail.gmail.com","threadId":"25209","inReplyTo":null,"subject":"git-svn error","fromName":"Nate Parsons","fromEmail":"parsons.nate@gmail.com","sentAt":"2010-09-23T14:30:22Z","receivedAt":"2010-09-23T14:30:22Z","isPatch":false,"sender":{"key":"parsons.nate@gmail.com","avatar":"https://gravatar.com/avatar/8fbd472c9e74c6f64c305d4ea09575011b36a7844737f47a36f59086d88646fb?d=mp&s=160"},"body":"Hi all,\n\nI'm experiencing an error message importing a new svn repository using\ncygwin git, version 1.7.2.3\n\n> fatal: refs/remotes/trunk: not a valid SHA1\n> update-ref refs/heads/master refs/remotes/trunk: command returned error: 128\n\nMy .git/config file (nothing looks amiss to me):\n[core]\n\trepositoryformatversion = 0\n\tfilemode = true\n\tbare = false\n\tlogallrefupdates = true\n\tignorecase = true\n[svn-remote \"svn\"]\n\turl = \n\tfetch = iem/procedures/iem:refs/remotes/trunk\n\tbranches = iem/procedures/Z_Folders/*:refs/remotes/*\n\nIt appears that this error was seen before in an older version that\ndidn't deal with extra \"/\"s appropriately, but I don't see that issue\nhere.\n\nThanks,\n-Nate\n"},{"id":"151387","messageId":"AANLkTi=KGtBJ=6-YWUJCsbmBWfnr1Kh2i=LaZmgM=8t5@mail.gmail.com","threadId":"25209","inReplyTo":"AANLkTi=5ficziLK8cfikotoxkgUDLfhAM_RLzCOcOv5U@mail.gmail.com","subject":"Re: git-svn error","fromName":"Nate Parsons","fromEmail":"parsons.nate@gmail.com","sentAt":"2010-09-23T19:45:49Z","receivedAt":"2010-09-23T19:45:49Z","isPatch":false,"sender":{"key":"parsons.nate@gmail.com","avatar":"https://gravatar.com/avatar/8fbd472c9e74c6f64c305d4ea09575011b36a7844737f47a36f59086d88646fb?d=mp&s=160"},"body":"Hi all,\n\nI reproduced the problem on openSUSE, running git 1.7.3. I can't\nprovide access to the subversion repository, but I can do anything\nelse to help diagnose the problem.\n\n-Nate\n\nOn Thu, Sep 23, 2010 at 10:30 AM, Nate Parsons wrote:\n> Hi all,\n>\n> I'm experiencing an error message importing a new svn repository using\n> cygwin git, version 1.7.2.3\n>\n>> fatal: refs/remotes/trunk: not a valid SHA1\n>> update-ref refs/heads/master refs/remotes/trunk: command returned error: 128\n>\n> My .git/config file (nothing looks amiss to me):\n> [core]\n>        repositoryformatversion = 0\n>        filemode = true\n>        bare = false\n>        logallrefupdates = true\n>        ignorecase = true\n> [svn-remote \"svn\"]\n>        url = \n>        fetch = iem/procedures/iem:refs/remotes/trunk\n>        branches = iem/procedures/Z_Folders/*:refs/remotes/*\n>\n> It appears that this error was seen before in an older version that\n> didn't deal with extra \"/\"s appropriately, but I don't see that issue\n> here.\n>\n> Thanks,\n> -Nate\n>\n"},{"id":"151443","messageId":"4C9C530D.3040206@drmicha.warpmail.net","threadId":"25209","inReplyTo":"AANLkTi=KGtBJ=6-YWUJCsbmBWfnr1Kh2i=LaZmgM=8t5@mail.gmail.com","subject":"Re: git-svn error","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-09-24T07:28:13Z","receivedAt":"2010-09-24T07:28:13Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Nate Parsons venit, vidit, dixit 23.09.2010 21:45:\n> Hi all,\n> \n> I reproduced the problem on openSUSE, running git 1.7.3. I can't\n> provide access to the subversion repository, but I can do anything\n> else to help diagnose the problem.\n\nHow about providing some context of that error message, i.e. a\ntransaction log? Also: Is this from a fresh repo?\n\nMichael\n"},{"id":"151543","messageId":"AANLkTikMsXhAJUU6tgcjMGdq2FGmgW3dXY_SS8=iMu2v@mail.gmail.com","threadId":"25209","inReplyTo":"4C9C530D.3040206@drmicha.warpmail.net","subject":"Re: git-svn error","fromName":"Nate Parsons","fromEmail":"parsons.nate@gmail.com","sentAt":"2010-09-24T20:33:36Z","receivedAt":"2010-09-24T20:33:36Z","isPatch":false,"sender":{"key":"parsons.nate@gmail.com","avatar":"https://gravatar.com/avatar/8fbd472c9e74c6f64c305d4ea09575011b36a7844737f47a36f59086d88646fb?d=mp&s=160"},"body":"On Fri, Sep 24, 2010 at 3:28 AM, Michael J Gruber\n wrote:\n>\n> Nate Parsons venit, vidit, dixit 23.09.2010 21:45:\n> > Hi all,\n> >\n> > I reproduced the problem on openSUSE, running git 1.7.3. I can't\n> > provide access to the subversion repository, but I can do anything\n> > else to help diagnose the problem.\n>\n> How about providing some context of that error message, i.e. a\n> transaction log? Also: Is this from a fresh repo?\n\nI'd be glad to do this, as long as nobody can use these logs to\nrecreate the contents of my repository. What commands do I run?\n\nThis is happening in a fresh repo, I do the 'git svn init' first, and\nthen 'git svn fetch $head' (where $head is actually a number). This is\nto work around my other git issue that hasn't gotten a response.\n\nI was able to fetch the entire repository using a combination of\nTortoiseGit (for the initial init and fetch, until it died with a file\npermissions error) and then fetch the rest of my history with msysgit,\nso this isn't a show-stopping issue for me.\n\n-Nate\n"}]}