Re: [BUG] git-svn dcommit fails (connection closed unexpectedly)
- From
- Martin Eisenhardt <list-receive@mneisen.org>
- Date
- May 13, 2007, 17:49 UTC
- Message-ID
- <200705131949.38051.list-receive@mneisen.org>
- In-Reply-To
- <20070513171707.GA14024@muzzle>
Hi Eric, hi Matthieu, hi list,
On Sunday 13 May 2007 19:17:07 Eric Wong wrote:
Show 9 quoted lines
> Matthieu Moy <Matthieu.Moy@imag.fr> wrote: > > 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 $
I ran into that one, too ... :-(
> > 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).
I assume that the dcommit runs fine for *other* commits but not for that one that produced the error cited above.
In my case, it was simply a problem on my side: I had tried to add a file, that already existed in the repository - and subversion rejected the commit. Of course, it would be nice if git-svn could simply tell the user about his error, i.e., simply copy the output of libsvn or whatever it is using to connect to the subversion repo.
Another case where I stumbled upon said error message was when I added an empty (sub)directory to a project in subversion and then used git to track that project. Since git cannot track an empty directory, it did not appear in my git working copy. When I mkdir'd the directory locally (in my git wc) and then tried to add files within that repository, I got exactly the same error as Matthieu.
> > Does the patch in > http://permalink.gmane.org/gmane.comp.version-control.git/47126 > help?
Not in my case, although this patch resolved the other issue, thanks again btw!
Kind regards Martin Eisenhardt