I was originally using ubuntu's package of git and git-svn (1.5.6.3)
and had the following Malformed Network Data error occuring at the
same spot.
I've since built svn and git so that I'm using the latest versions of
each svn: 1.5.5 and git: 1.6.1.2.390.gba743
With the latest version I got a new error during the initial clone
followed by the original error.
One thing to note that I thought was odd. The clone starts at ~r977
and proceeded through about ~r1100 before starting over at r1 and
running all the way up to the code you see below (r1116)
Is this a git issues or is it possible the svn repo is corrupted
somehow? Any way I can get around this?
Thanks!
$ git svn clone -s svn+ssh://.../community_
service
r1116 = 890ff1e819be8ae0a752f53ba2103171de41fc69 (trunk)
M sample_data/activities.yml
r1117 = ab725a6c32905b6d007fcd8fd4723058d9487706 (trunk)
Found possible branch point: svn+ssh://.../community_service/trunk =>
svn+ssh://.../community_service/branches/current_demo, 1118
Found branch parent: (current_demo) ab725a6c32905b6d007fcd8fd4723058d9487706
Index mismatch: e8075b5d0694a738392d84016922eca87db65dcd !=
44b21b4a4fa70455621da3ac159cdf42c8c59987
rereading ab725a6c32905b6d007fcd8fd4723058d9487706
Following parent with do_switch
Filesystem has no item: File not found: revision 1036, path
'/branches/current_demo/sample_data/email_templates.yml' at
/usr/local/libexec/git-core/git-svn line 3288
$ cd community_service/
$ git svn fetch
Found possible branch point: svn+ssh://.../community_service/trunk =>
svn+ssh://.../community_service/branches/current_demo, 1118
Found branch parent: (current_demo) ab725a6c32905b6d007fcd8fd4723058d9487706
Index mismatch: e8075b5d0694a738392d84016922eca87db65dcd !=
44b21b4a4fa70455621da3ac159cdf42c8c59987
rereading ab725a6c32905b6d007fcd8fd4723058d9487706
Following parent with do_switch
Malformed network data: Malformed network data at
/usr/local/libexec/git-core/git-svn line 3288
--
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
