{"thread":{"id":"9018","subject":"git-svn: failure to clone logcheck's repo","startedAt":"2007-07-13T09:36:22Z","lastAt":"2007-07-13T10:37:14Z","messageCount":4,"participants":["martin f krafft","Peter Baumann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"47247","messageId":"20070713093622.GA21001@lapse.madduck.net","threadId":"9018","inReplyTo":null,"subject":"git-svn: failure to clone logcheck's repo","fromName":"martin f krafft","fromEmail":"madduck@madduck.net","sentAt":"2007-07-13T09:36:22Z","receivedAt":"2007-07-13T09:36:22Z","isPatch":false,"sender":{"key":"madduck@madduck.net","avatar":null},"body":"Hi list,\n\nI am trying to access the logcheck repository with git-svn. Even\nthough I can happily clone the trunk:\n\n  git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git\n\nas soon as I try to clone the entire thing with tags and branches:\n\n  git-svn clone -T trunk -t tags -b branches\n    svn://svn.debian.org/svn/logcheck/logcheck git\n\nit barfs:\n\n  Initialized empty Git repository in .git/\n  Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck\n  r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)\n  [...]\n  r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)\n  Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20\n  Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330\n  Following parent with do_switch\n  Successfully followed parent\n  r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)\n  Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029\n\nI think I'll be fine with *not* preserving logcheck's history when\nI move it to git, but thought best to let you know since this may be\na bug in git-svn.\n\nCheers,\n\n-- \nmartin;              (greetings from the heart of the sun.)\n  \\____ echo mailto: !#^.\"<*>\"|tr \"<*> mailto:\" net@madduck\n \nspamtraps: madduck.bogus@madduck.net\n \nwindoze is the one-night-stand of operating systems;\nyou feel so cheap after having used it.\n"},{"id":"47248","messageId":"20070713094710.GB18199@xp.machine.xx","threadId":"9018","inReplyTo":"20070713093622.GA21001@lapse.madduck.net","subject":"Re: git-svn: failure to clone logcheck's repo","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2007-07-13T09:47:10Z","receivedAt":"2007-07-13T09:47:10Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Fri, Jul 13, 2007 at 11:36:22AM +0200, martin f krafft wrote:\n> Hi list,\n> \n> I am trying to access the logcheck repository with git-svn. Even\n> though I can happily clone the trunk:\n> \n>   git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git\n> \n> as soon as I try to clone the entire thing with tags and branches:\n> \n>   git-svn clone -T trunk -t tags -b branches\n>     svn://svn.debian.org/svn/logcheck/logcheck git\n> \n> it barfs:\n> \n>   Initialized empty Git repository in .git/\n>   Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck\n>   r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)\n>   [...]\n>   r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)\n>   Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20\n>   Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330\n>   Following parent with do_switch\n>   Successfully followed parent\n>   r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)\n>   Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029\n> \n> I think I'll be fine with *not* preserving logcheck's history when\n> I move it to git, but thought best to let you know since this may be\n> a bug in git-svn.\n> \n\nThis is a known problem. If I remember correctly,it is save to just\nresume the import with git-svn fetch, and nothing bad should happen.\n\nJust search the list archive for more info (sorry, I don't have a\nreference to the thread)\n\n-Peter\n"},{"id":"47249","messageId":"20070713095620.GC18199@xp.machine.xx","threadId":"9018","inReplyTo":"20070713094710.GB18199@xp.machine.xx","subject":"Re: git-svn: failure to clone logcheck's repo","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2007-07-13T09:56:20Z","receivedAt":"2007-07-13T09:56:20Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Fri, Jul 13, 2007 at 11:47:10AM +0200, Peter Baumann wrote:\n> On Fri, Jul 13, 2007 at 11:36:22AM +0200, martin f krafft wrote:\n> > Hi list,\n> > \n> > I am trying to access the logcheck repository with git-svn. Even\n> > though I can happily clone the trunk:\n> > \n> >   git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git\n> > \n> > as soon as I try to clone the entire thing with tags and branches:\n> > \n> >   git-svn clone -T trunk -t tags -b branches\n> >     svn://svn.debian.org/svn/logcheck/logcheck git\n> > \n> > it barfs:\n> > \n> >   Initialized empty Git repository in .git/\n> >   Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck\n> >   r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)\n> >   [...]\n> >   r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)\n> >   Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20\n> >   Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330\n> >   Following parent with do_switch\n> >   Successfully followed parent\n> >   r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)\n> >   Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029\n> > \n> > I think I'll be fine with *not* preserving logcheck's history when\n> > I move it to git, but thought best to let you know since this may be\n> > a bug in git-svn.\n> > \n> \n> This is a known problem. If I remember correctly,it is save to just\n> resume the import with git-svn fetch, and nothing bad should happen.\n> \n> Just search the list archive for more info (sorry, I don't have a\n> reference to the thread)\n\nJust found it. Look e.g. here on the comment from Eric Wong:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/50962/focus=275913\n\n-Peter\n"},{"id":"47256","messageId":"20070713103714.GA30474@lapse.madduck.net","threadId":"9018","inReplyTo":"20070713095620.GC18199@xp.machine.xx","subject":"Re: git-svn: failure to clone logcheck's repo","fromName":"martin f krafft","fromEmail":"madduck@madduck.net","sentAt":"2007-07-13T10:37:14Z","receivedAt":"2007-07-13T10:37:14Z","isPatch":false,"sender":{"key":"madduck@madduck.net","avatar":null},"body":"also sprach Peter Baumann <waste.manager@gmx.de> [2007.07.13.1147 +0200]:\n> This is a known problem. If I remember correctly,it is save to\n> just resume the import with git-svn fetch, and nothing bad should\n> happen.\n\nYeah, this seems to work.\n\n> Just found it. Look e.g. here on the comment from Eric Wong:\n> \n> http://thread.gmane.org/gmane.comp.version-control.git/50962/focus=275913\n\nShame on me, I really should have done the research myself. I guess\nI am still too overwhelmed with git, but that won't last long,\nI promise.\n\n-- \nmartin;              (greetings from the heart of the sun.)\n  \\____ echo mailto: !#^.\"<*>\"|tr \"<*> mailto:\" net@madduck\n \nspamtraps: madduck.bogus@madduck.net\n \n\"lessing was a heretics' heretic\" \n                                                    -- walter kaufmann\n"}]}