git svn dcommit seg fault

git svn dcommit seg fault

[Perrin Meyer]

I'm able to clone svn repo's fine with

$ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/ .

and I'm then able to use git commit to commit local changes, but 
when I try 

$ git svn dcommit

I get

[perrin@whisper TESTGIT]$ git svn dcommit
        M       test.c
Committed r717
Segmentation fault

As far as I can tell, the commit worked fine (verified by trying 'svn update' on another box).

I've tried git version 1.5.2.3, 1.5.3-rc2, and the latest build, and all give the seg fault. 

I'm guessing it has something to do with using the https connection to svn?

Thanks,

Perrin Meyer

Re: git svn dcommit seg fault

[Eric Wong]

Perrin Meyer <perrinmeyer@yahoo.com> wrote:
> 
> I'm able to clone svn repo's fine with
> 
> $ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/ .
> 
> and I'm then able to use git commit to commit local changes, but 
> when I try 
> 
> $ git svn dcommit
> 
> I get
> 
> [perrin@whisper TESTGIT]$ git svn dcommit
>         M       test.c
> Committed r717
> Segmentation fault


> As far as I can tell, the commit worked fine (verified by trying 'svn
> update' on another box).
> 
> I've tried git version 1.5.2.3, 1.5.3-rc2, and the latest build, and
> all give the seg fault.
> 
> I'm guessing it has something to do with using the https connection to
> svn?

I primarily work with https repositories using git-svn and I haven't
seen any segfaults in a while.  Which version of the SVN libraries do
you have?  (git-svn --version will tell you).

-- 
Eric Wong

Re: git svn dcommit seg fault

[Perrin Meyer]

I did some more investigating on why git svn dcommit was seg faulting
for me, and I noticed that when I do my initial git svn clone 

$ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/
TESTGIT_GIT/   

I always get an error
W: Ignoring error from SVN, path probably does not exist: (175007):
HTTP Path Not Found: REPORT request failed on
'/perrin/!svn/bc/100/trunk/TESTGIT':
'/perrin/!svn/bc/100/trunk/TESTGIT' path not found

This makes sense, since I did move my repo around a while back. Could
this be causing the seg fault problem I'm having with git svn
dcommit?

Just to be sure, I created a directory on our svn server's TEST2
repo, and I was able to use git svn to commit to it with git svn
dcommit just fine, so I think my git and svn setup is correct.

[perrin@whisper perrintest2_GIT]$ git svn dcommit
        M       testgit.c
Committed r130
        M       testgit.c
r130 = 01985d82b738b79bb479ef8817200ebe7c79eb94 (git-svn)
No changes between current HEAD and refs/remotes/git-svn
Resetting to the latest refs/remotes/git-svn

Thanks,

Perrin




--- Eric Wong <eric@petta-tech.com> wrote:

> Perrin Meyer <perrinmeyer@yahoo.com> wrote:
> > 
> > I'm able to clone svn repo's fine with
> > 
> > $ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/ .
> > 
> > and I'm then able to use git commit to commit local changes, but 
> > when I try 
> > 
> > $ git svn dcommit
> > 
> > I get
> > 
> > [perrin@whisper TESTGIT]$ git svn dcommit
> >         M       test.c
> > Committed r717
> > Segmentation fault
> 
> 
> > As far as I can tell, the commit worked fine (verified by trying
> 'svn
> > update' on another box).
> > 
> > I've tried git version 1.5.2.3, 1.5.3-rc2, and the latest build,
> and
> > all give the seg fault.
> > 
> > I'm guessing it has something to do with using the https
> connection to
> > svn?
> 
> I primarily work with https repositories using git-svn and I
> haven't
> seen any segfaults in a while.  Which version of the SVN libraries
> do
> you have?  (git-svn --version will tell you).
> 
> -- 
> Eric Wong
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: git svn dcommit seg fault

[Perrin Meyer]

[perrin@whisper TESTGIT]$ git svn --version
git-svn version 1.5.3.rc2.4.g726f9 (svn 1.2.3)

I get the "post commit" email from our SVN central server, so it appears that on the SVN side the commit worked? 

I tried running git svn with --verbose, but that did not print out any more error messages (besides the seg fault).

Thanks,

Perrin



----- Original Message ----
From: Eric Wong <eric@petta-tech.com>
To: Perrin Meyer <perrinmeyer@yahoo.com>
Cc: git@vger.kernel.org
Sent: Wednesday, July 18, 2007 12:34:50 AM
Subject: Re: git svn dcommit seg fault

Perrin Meyer <perrinmeyer@yahoo.com> wrote:
> 
> I'm able to clone svn repo's fine with
> 
> $ git svn clone https://svn.eng.msli.com/perrin/trunk/TESTGIT/ .
> 
> and I'm then able to use git commit to commit local changes, but 
> when I try 
> 
> $ git svn dcommit
> 
> I get
> 
> [perrin@whisper TESTGIT]$ git svn dcommit
>         M       test.c
> Committed r717
> Segmentation fault


> As far as I can tell, the commit worked fine (verified by trying 'svn
> update' on another box).
> 
> I've tried git version 1.5.2.3, 1.5.3-rc2, and the latest build, and
> all give the seg fault.
> 
> I'm guessing it has something to do with using the https connection to
> svn?

I primarily work with https repositories using git-svn and I haven't
seen any segfaults in a while.  Which version of the SVN libraries do
you have?  (git-svn --version will tell you).

-- 
Eric Wong