Matthieu Moy <Matthieu.Moy@xxxxxxx> wrote: > Hi, > > I'm using git-svn, which usually works fine, but I occasionally get > this: > > $ git-svn dcommit > A file1 > A file2 > Network connection closed unexpectedly: Connection closed unexpectedly at /path/to/git-svn line 401 > $ > > The failure seems to depend on the commit's I'm pushing, since this is > reproducible when running several times "dcommit" for the same commit, > but the same command also usually works fine on the same repositories > (same git repo, same svn target). > > The svn repository is accessed with svn+ssh://user@machine/path/. Does the patch in http://permalink.gmane.org/gmane.comp.version-control.git/47126 help? If so, I'm not sure why it should be failing sometimes and not all the time. If your local username the same as the username you're using for svn it shouldn't fail for the reason that patch above is needed. Using the native svn or svn+ssh protocol is definitely flakier in my experience, and there are still known issues with connections closing during *fetch*. dcommit is actually a lot more straightforward as it only connects once, whereas fetch can reconnect to different parts of the repo for --follow-parent. > exporting the patch, applying it to an svn checkout, and "svn commit" > works fine. > > Let me know if I can provide any other usefull information for > debugging. > > Thanks, > > Debian etch (stable) > Reproducible with both git 1.5.1.1 and the latest from git: > > $ git-svn --version > git-svn version 1.5.2.rc3.3.ge347 (svn 1.4.2) Which version of SVN is running on the server? -- Eric Wong - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
