# git-svn: failure to clone logcheck's repo 4 messages from 2007-07-13 to 2007-07-13. Participants: martin f krafft, Peter Baumann. Thread: https://gitlist.dev/t/9018 ## martin f krafft, 2007-07-13 09:36 Subject: git-svn: failure to clone logcheck's repo Message-ID: <20070713093622.GA21001@lapse.madduck.net> URL: https://gitlist.dev/e/20070713093622.GA21001%40lapse.madduck.net ``` 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. Cheers, -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus@madduck.net windoze is the one-night-stand of operating systems; you feel so cheap after having used it. ``` ## Peter Baumann, 2007-07-13 09:47 Subject: Re: git-svn: failure to clone logcheck's repo Message-ID: <20070713094710.GB18199@xp.machine.xx> URL: https://gitlist.dev/e/20070713094710.GB18199%40xp.machine.xx In-Reply-To: <20070713093622.GA21001@lapse.madduck.net> ``` 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) -Peter ``` ## Peter Baumann, 2007-07-13 09:56 Subject: Re: git-svn: failure to clone logcheck's repo Message-ID: <20070713095620.GC18199@xp.machine.xx> URL: https://gitlist.dev/e/20070713095620.GC18199%40xp.machine.xx In-Reply-To: <20070713094710.GB18199@xp.machine.xx> ``` 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 ``` ## martin f krafft, 2007-07-13 10:37 Subject: Re: git-svn: failure to clone logcheck's repo Message-ID: <20070713103714.GA30474@lapse.madduck.net> URL: https://gitlist.dev/e/20070713103714.GA30474%40lapse.madduck.net In-Reply-To: <20070713095620.GC18199@xp.machine.xx> ``` also sprach Peter Baumann [2007.07.13.1147 +0200]: > 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. Yeah, this seems to work. > 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 Shame on me, I really should have done the research myself. I guess I am still too overwhelmed with git, but that won't last long, I promise. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus@madduck.net "lessing was a heretics' heretic" -- walter kaufmann ```