Re: git-svn woes

Deskin Miller [off-list ref] wrote:

On Fri, Feb 27, 2009 at 15:37, Nicolas Pitre [off-list ref] wrote:

quoted

OK... I cannot pretend to be a newbie with git.  However it's the first
time I try git-svn and it looks like a couple basic things aren't right.

I initially cloned svn://svn.berlios.de/openocd using "git svn clone -s".
So far so good.  Now I'm attempting to update using "git svn fetch" but
the operation always fails with the following error:

|branch_from: /openocd/branches => /openocd/branches/xscale
|Found possible branch point:
|svn://svn.berlios.de/openocd/openocd/branches/xscale =>
|svn://svn.berlios.de/openocd/branches/xscale, 1231
|Initializing parent: xscale@1231
|Found branch parent: (xscale) 657522f3f2d1ab8b679fd5b45ce4e9ca1974af18
|Following parent with do_switch
|Scanning for empty symlinks, this may take a while if you have many empty files
|You may disable this with `git config svn.brokenSymlinkWorkaround false'.
|This may be done in a different terminal without restarting git svn
|Malformed network data: Malformed network data at /home/nico/libexec/git-core/git-svn line 3333

I experience the same error as you do with 1.6.2-rc2.  This error is
occurring in the new broken-symlink-workaround code.  I'm not sure
what is going on and don't have time to examine it closely, but the
function where the error occurs doesn't run if the config
svn.brokenSymlinkWorkaround option is set false; doing so makes the
fetch continue for me.

Any ideas, Eric?

I've been poking around at this for a bit, I am pretty confused
by this, too.  It's been a rough week, so I could be missing
something obvious...

Junio: since 1.6.2 might be out the door before we have time to resolve
this, I'm leaning towards disabling the broken-symlink-workaround by
default for the release. It seems far more people are negatively
affected by the attempted fix around this rare problem than helped.

quoted

Thing is... the repository never gets updated and by far.  According to
"git svn info", the fetched revision is 1232, while a separate
repository using native svn claims to be at revision 1383.

Furthermore, the "git svn info" command produces yet more errors, such
as:

|Use of uninitialized value $lc_author in concatenation (.) or string at /home/nico/libexec/git-core/git-svn line 964.
|Use of uninitialized value $lc_rev in concatenation (.) or string at /home/nico/libexec/git-core/git-svn line 965.
|Use of uninitialized value $t in gmtime at /home/nico/libexec/git-core/git-svn line 4743.
|Use of uninitialized value $t in numeric comparison (<=>) at /home/nico/libexec/git-core/git-svn line 4744.
|Use of uninitialized value $t in subtraction (-) at /home/nico/libexec/git-core/git-svn line 4745.
|Use of uninitialized value $t in localtime at /home/nico/libexec/git-core/git-svn line 4746.

This is with git from current "next". I cannot spend time to try fixing
the issue myself (especially as I'm not familiar at all with the inner
workings of svn), so my only option at the moment is to give up on
git-svn altogether.  :-(

Oh, don't give up quite yet :)

Deskin Miler

-- 
Eric Wong