Re: git-svn: failure to clone logcheck's repo

[Peter Baumann <waste.manager@xxxxxx>]

On Fri, Jul 13, 2007 at 11:47:10AM +0200, Peter Baumann wrote:
> On Fri, Jul 13, 2007 at 11:36:22AM +0200, martin f krafft wrote:
> > Hi list,
> > 
> > I am trying to access the logcheck repository with git-svn. Even
> > though I can happily clone the trunk:
> > 
> >   git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git
> > 
> > as soon as I try to clone the entire thing with tags and branches:
> > 
> >   git-svn clone -T trunk -t tags -b branches
> >     svn://svn.debian.org/svn/logcheck/logcheck git
> > 
> > it barfs:
> > 
> >   Initialized empty Git repository in .git/
> >   Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck
> >   r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)
> >   [...]
> >   r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)
> >   Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20
> >   Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330
> >   Following parent with do_switch
> >   Successfully followed parent
> >   r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)
> >   Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029
> > 
> > I think I'll be fine with *not* preserving logcheck's history when
> > I move it to git, but thought best to let you know since this may be
> > a bug in git-svn.
> > 
> 
> This is a known problem. If I remember correctly,it is save to just
> resume the import with git-svn fetch, and nothing bad should happen.
> 
> Just search the list archive for more info (sorry, I don't have a
> reference to the thread)

Just found it. Look e.g. here on the comment from Eric Wong:

http://thread.gmane.org/gmane.comp.version-control.git/50962/focus=275913

-Peter
-
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