{"thread":{"id":"29336","subject":"git svn clone terminating prematurely (I think)","startedAt":"2012-01-11T00:02:09Z","lastAt":"2012-01-13T07:10:15Z","messageCount":6,"participants":["Steven Line","Ramkumar Ramachandra","Jonathan Nieder","Steven Michalske"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"182294","messageId":"CAJ1a7SrkDOyNRv8Spo4xvoKjP4zaXteim4h3JGcWU-nYDugx9Q@mail.gmail.com","threadId":"29336","inReplyTo":null,"subject":"git svn clone terminating prematurely (I think)","fromName":"Steven Line","fromEmail":"sline00@gmail.com","sentAt":"2012-01-11T00:02:09Z","receivedAt":"2012-01-11T00:02:09Z","isPatch":false,"sender":{"key":"sline00@gmail.com","avatar":null},"body":"Reposting this with a better subject than (unknown) . . .\n\nHi All,\n\nFirst off I am a new user to git, I'm not a git developer or power\nuser.  Am I in the right mailing list?  If not could somebody point me\nwhere I could get some help from experienced git people?\n\nHere's the problem:\nI need some help getting my subversion repository cloned over to git.\nOur svn repository has about 12,000 commits, when I run\ngit svn clone -s  -A authors.txt\nsvn+ssh://csvn <at> source.res.ourdomain.com/home/svn/sem sem\nIt runs for about 2h 15m then completes with no error messages. I have\nalso cloned starting at revision 6300, about the middle of the svn\nrepository, and I get the same results as below.\n\nAfter cloning, I cd into the sem directory and run\n\n$ git log\nfatal: bad default revision 'HEAD'\n\n$ git log --all  # this seems to work\n\n$ git branch -a # shows only about half the branches that should have\nbeen cloned\n\n$ ls -al sem\ntotal 6\ndrwxr-xr-x   3 git      other        512 Jan 10 20:58 ./\ndrwxr-xr-x   6 git      root         512 Jan 10 20:58 ../\ndrwxr-xr-x   9 git      other        512 Jan 10 23:13 .git/\n\nI think this means the clone terminated prematurely but other than\nthat I'm stuck. There were no error messages from the clone.  Could\nsomebody give me some suggestions on what to try?  I haven't found the\nanswer via google yet.\n\nThank you for any help.\n\n-- \nSteven Line\n303-910-1212\nsline00@gmail.com\n"},{"id":"182311","messageId":"CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com","threadId":"29336","inReplyTo":"CAJ1a7SrkDOyNRv8Spo4xvoKjP4zaXteim4h3JGcWU-nYDugx9Q@mail.gmail.com","subject":"Re: git svn clone terminating prematurely (I think)","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2012-01-11T04:34:26Z","receivedAt":"2012-01-11T04:34:26Z","isPatch":false,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Hi Steven,\n\nSteven Line wrote:\n> First off I am a new user to git, I'm not a git developer or power\n> user.  Am I in the right mailing list?  If not could somebody point me\n> where I could get some help from experienced git people?\n\nThis is the right place.  The Git community believes in maintaining\njust one mailing list.\n\n> I need some help getting my subversion repository cloned over to git.\n> Our svn repository has about 12,000 commits, when I run\n> git svn clone -s  -A authors.txt\n> svn+ssh://csvn <at> source.res.ourdomain.com/home/svn/sem sem\n> It runs for about 2h 15m then completes with no error messages. I have\n> also cloned starting at revision 6300, about the middle of the svn\n> repository, and I get the same results as below.\n\n> $ git branch -a # shows only about half the branches that should have\n> been cloned\n\nInteresting.  From the git-svn-id of the most recent commit, can you\ntell if there's anything especially fishy about the revision where\ngit-svn stops?  Your Subversion repository is probably broken in some\nway, but git-svn should not use that as an excuse for appearing to\nfinish successfully while failing in reality.\n\nCheers.\n\n-- Ram\n"},{"id":"182382","messageId":"CAJ1a7SoW0vNBR2gaBPCA5RqU7_LnQ5pMmgihZ_sKF09+Cj3Stg@mail.gmail.com","threadId":"29336","inReplyTo":"CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com","subject":"Re: git svn clone terminating prematurely (I think)","fromName":"Steven Line","fromEmail":"sline00@gmail.com","sentAt":"2012-01-11T21:52:26Z","receivedAt":"2012-01-11T21:52:26Z","isPatch":false,"sender":{"key":"sline00@gmail.com","avatar":null},"body":"Hi Ram, thank you for the reply.  Se below . . .\n\n>\n>> I need some help getting my subversion repository cloned over to git.\n>> Our svn repository has about 12,000 commits, when I run\n>> git svn clone -s  -A authors.txt\n>> svn+ssh://csvn <at> source.res.ourdomain.com/home/svn/sem sem\n>> It runs for about 2h 15m then completes with no error messages. I have\n>> also cloned starting at revision 6300, about the middle of the svn\n>> repository, and I get the same results as below.\n>\n>> $ git branch -a # shows only about half the branches that should have\n>> been cloned\n>\n> Interesting.  From the git-svn-id of the most recent commit, can you\n> tell if there's anything especially fishy about the revision where\n> git-svn stops?  Your Subversion repository is probably broken in some\n> way, but git-svn should not use that as an excuse for appearing to\n> finish successfully while failing in reality.\n\nWell by your question it seems you expect this clone to fail at the\nsame svn revision number\neach time.  I spent all day today trying to figure out what that\nrevision was. However it doesn't\nseem to be failing at the same svn revision each time.\n\nThere are about 12813 revisions in our svn repository so I started\nattempting clones from successively later\nand later revisions both to figure which revision they repeatedly\nfailed on (it was never the same one) and to see\nif I could coax a successful clone to occur.  Originally I started at\nrevision 1, then incremented to 6300, then 8000, then 10000, then\n12,500, then finally 12,700.  Finally the attempt starting at svn\nrevision 12,700 succeeded and the resulting git repository\nseems to work. All the attempts prior to 12,700 (starting at 1, 6300,\n8000, 10000, and 12,500) failed while\nimporting different revisions, none of them showed error messages.\n\nOne thing that I am suspect of is that I'm not able to log directly\ninto the machine running git, it's on a remote server in\nAtlanta while I'm in Colorado. I'm running the 'git svn clone' using\nnohup, but in every case of a corrupt git repository\nthe connection between me and the server dies before the git completes\n(the connection dies, but I log in again and run\nps -ef and I see the multiple git processes still running.  They run\nfor up to several hours longer, then terminate).  I should be\nok since I'm using nohup, but coincidentally the only clone that\nsucceeded was the one where the network connection\nnever disconnected during the clone\n\nNot sure if this helps but here are some numbers:\nBoth the svn repository and git machine are Solaris 10\nSvn revision 1.6.12 CollabNet\nGit version 1.7.6.1\n\nThank you.\n\n\n-- \nSteven Line\n303-910-1212\nsline00@gmail.com\n"},{"id":"182383","messageId":"20120111224833.GA29654@burratino","threadId":"29336","inReplyTo":"CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com","subject":"Re: git svn clone terminating prematurely (I think)","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2012-01-11T22:48:33Z","receivedAt":"2012-01-11T22:48:33Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Ramkumar Ramachandra wrote:\n\n> Interesting.  From the git-svn-id of the most recent commit, can you\n> tell if there's anything especially fishy about the revision where\n> git-svn stops?  Your Subversion repository is probably broken in some\n> way,\n\nI wouldn't necessarily assume that.  My first hunch would have been\nthat this is some variation on the SIGPIPE bug[1].  The usual\nworkaround for that[2] is to get git-svn to continue by running \"git\nsvn fetch\" again.  Nobody's fixed it because nobody's stared at the\nSVN perl bindings for long enough to find the cause.\n\nModern git versions produce a message in that case, though:\n\n\terror: git-svn died of signal 13\n\nSo you are probably running into something else.  I only mention this\nfor context.\n\nDoes svnsync work for making a local copy of whatever subset of the\nrepository is relevant?  Alternatively (this is basically the same),\nis the network connection stable enough for e.g. svnrdump[3] to get a\ndump?\n\nSorry for the trouble, and hope that helps,\nJonathan\n\n[1] http://thread.gmane.org/gmane.comp.version-control.git/134936/focus=134940\n[2] Maybe it deserves a note in the manpage.\n[3] http://repo.or.cz/w/svnrdump.git\n"},{"id":"182449","messageId":"CAJ1a7SpRP5GymPrpEchuNk3xwkJLHBKjsXY_85Xs_LAzXtWYuw@mail.gmail.com","threadId":"29336","inReplyTo":"20120111224833.GA29654@burratino","subject":"Re: git svn clone terminating prematurely (I think)","fromName":"Steven Line","fromEmail":"sline00@gmail.com","sentAt":"2012-01-12T18:25:18Z","receivedAt":"2012-01-12T18:25:18Z","isPatch":false,"sender":{"key":"sline00@gmail.com","avatar":null},"body":"Thank you Jonathan.\n\nI had a breakthrough yesterday on this problem.  To make a long story\nshort my ssh connection to the server where I was running 'nohup git\nsvn clone' was timing out.  Additionally the nohup I was using wasn't\nreally protecting the git svn clone process so an hour or two after\nthe ssh disconnected, the git would terminate leaving me with an\nimcomplete repository.  I don't understand why the nohup wasn't\nworking yet.  So my problem wasn't due to git itself.\n\nI started my most recent git svn clone and it's now been running for\n18 hours.  I'm optimistic that I've solved the problem.  If my git\ndoes terminate early then I'll try a 'git svn fetch' to complete the\nclone, based on what you said in your post.\n\n-- \nSteven Line\n303-910-1212\nsline00@gmail.com\n"},{"id":"182479","messageId":"FDD0F00A-8BD3-466A-95A6-03FBEE0E068D@gmail.com","threadId":"29336","inReplyTo":"CAJ1a7SpRP5GymPrpEchuNk3xwkJLHBKjsXY_85Xs_LAzXtWYuw@mail.gmail.com","subject":"Re: git svn clone terminating prematurely (I think)","fromName":"Steven Michalske","fromEmail":"smichalske@gmail.com","sentAt":"2012-01-13T07:10:15Z","receivedAt":"2012-01-13T07:10:15Z","isPatch":false,"sender":{"key":"smichalske@gmail.com","avatar":"https://gravatar.com/avatar/721f27456adc9ac84f3bb235f021a70015abb9e09222ae8622fc5579c6a203c1?d=mp&s=160"},"body":"Steven, \n\nIn this case nohup seems like a pain.  There is a utility called \"screen\" available on most unixes.\nIt allows you to create a virtual terminal that you can detach from.  After you detach you can log out, some time later log back in and then reattach.\n\nSteve\n\nOn Jan 12, 2012, at 10:25 AM, Steven Line wrote:\n\n> Thank you Jonathan.\n> \n> I had a breakthrough yesterday on this problem.  To make a long story\n> short my ssh connection to the server where I was running 'nohup git\n> svn clone' was timing out.  Additionally the nohup I was using wasn't\n> really protecting the git svn clone process so an hour or two after\n> the ssh disconnected, the git would terminate leaving me with an\n> imcomplete repository.  I don't understand why the nohup wasn't\n> working yet.  So my problem wasn't due to git itself.\n> \n> I started my most recent git svn clone and it's now been running for\n> 18 hours.  I'm optimistic that I've solved the problem.  If my git\n> does terminate early then I'll try a 'git svn fetch' to complete the\n> clone, based on what you said in your post.\n> \n> -- \n> Steven Line\n> 303-910-1212\n> sline00@gmail.com\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"}]}