# Problems with "git svn clone" 5 messages from 2016-10-17 to 2016-10-21. Participants: K Richard Pixley, Eric Wong. Thread: https://gitlist.dev/t/44315 ## K Richard Pixley, 2016-10-17 21:03 Subject: Problems with "git svn clone" Message-ID: <500ef24a-55f9-1b38-52bb-17347ebaabcd@zebra.com> URL: https://gitlist.dev/e/500ef24a-55f9-1b38-52bb-17347ebaabcd%40zebra.com ``` I'm trying to create a git-svn repository with: git svn clone --username=pixleyr --stdlayout --branches branches --branches branches2 svn://mumble.com/mumble/mumble but the command dies about 11seconds in with: A src/kernel/ppc/2.4.26-pre5-moto-pq3-2004_06_04-0/drivers/usb/serial/belkin_sa.h A src/kernel/ppc/2.4.26-pre5-moto-pq3-2004_06_04-0/drivers/usb/serial/keyspan_usa28_fw.h error: git-svn died of signal 11 This seems awfully early and blatant for a core dump. What can I do to get this running? Initially discovered on git-2.7.4, (ubuntu-16.04), but also reproduced on freshly built top of tree git-2.10.1.445.g3cdd5d1. --rich ________________________________ - CONFIDENTIAL- This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email. ``` ## Eric Wong, 2016-10-19 20:41 Subject: Re: Problems with "git svn clone" Message-ID: <20161019204118.GA5982@starla> URL: https://gitlist.dev/e/20161019204118.GA5982%40starla In-Reply-To: <500ef24a-55f9-1b38-52bb-17347ebaabcd@zebra.com> ``` K Richard Pixley wrote: > error: git-svn died of signal 11 > > This seems awfully early and blatant for a core dump. What can I do to > get this running? Can you show us a backtrace? Thanks. > Initially discovered on git-2.7.4, (ubuntu-16.04), but also reproduced > on freshly built top of tree git-2.10.1.445.g3cdd5d1. This could be a problem with the SVN Perl libraries, and should be fixed in newer versions (not sure if it's made it to distros, yet): https://public-inbox.org/git/0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net/T/ Seems like it is fixed in latest Debian, maybe it needs to trickle into Ubuntu: https://bugs.debian.org/780246 ``` ## K Richard Pixley, 2016-10-19 20:49 Subject: Re: Problems with "git svn clone" Message-ID: URL: https://gitlist.dev/e/dea3ab60-be6b-ebcc-1047-6ab28a25979b%40zebra.com In-Reply-To: <20161019204118.GA5982@starla> ``` On 10/19/16 13:41 , Eric Wong wrote: > K Richard Pixley wrote: >> error: git-svn died of signal 11 >> >> This seems awfully early and blatant for a core dump. What can I do to >> get this running? > Can you show us a backtrace? Thanks. There is none. I ran it in gdb and bt produced no results. Nor did the thread send bt command. >> Initially discovered on git-2.7.4, (ubuntu-16.04), but also reproduced >> on freshly built top of tree git-2.10.1.445.g3cdd5d1. > This could be a problem with the SVN Perl libraries, and should > be fixed in newer versions (not sure if it's made it to distros, > yet): > > https://public-inbox.org/git/0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net/T/ > > Seems like it is fixed in latest Debian, maybe it needs to trickle > into Ubuntu: https://bugs.debian.org/780246 Thanks. I'll try adding that. Er... which debian would that be? testing? Or sid? --rich ________________________________ - CONFIDENTIAL- This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email. ``` ## Eric Wong, 2016-10-20 00:49 Subject: Re: Problems with "git svn clone" Message-ID: <20161020004956.GA8083@starla> URL: https://gitlist.dev/e/20161020004956.GA8083%40starla In-Reply-To: ``` K Richard Pixley wrote: > On 10/19/16 13:41 , Eric Wong wrote: > >K Richard Pixley wrote: > >>error: git-svn died of signal 11 > >> > >>This seems awfully early and blatant for a core dump. What can I do to > >>get this running? > >Can you show us a backtrace? Thanks. > There is none. I ran it in gdb and bt produced no results. Nor did the > thread send bt command. You probably need to install the debug package(s) for subversion. In case it's a different bug, maybe the debug package for Perl, too. > >>Initially discovered on git-2.7.4, (ubuntu-16.04), but also reproduced > >>on freshly built top of tree git-2.10.1.445.g3cdd5d1. > >This could be a problem with the SVN Perl libraries, and should > >be fixed in newer versions (not sure if it's made it to distros, > >yet): > > > >https://public-inbox.org/git/0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net/T/ > > > >Seems like it is fixed in latest Debian, maybe it needs to trickle > >into Ubuntu: https://bugs.debian.org/780246 > Thanks. I'll try adding that. > > Er... which debian would that be? testing? Or sid? It looks like it (1.9.4-3) has trickled into stretch (testing) by now: https://packages.debian.org/src:subversion ``` ## K Richard Pixley, 2016-10-21 16:33 Subject: Re: Problems with "git svn clone" Message-ID: <3ef5b7e2-5b34-e6e5-d75c-757d17ff10ce@zebra.com> URL: https://gitlist.dev/e/3ef5b7e2-5b34-e6e5-d75c-757d17ff10ce%40zebra.com In-Reply-To: <20161020004956.GA8083@starla> ``` Thank you. Running on debian stretch/testing it got past the 11 second mark and has been running for a day now. I expect it will take days, perhaps longer, so we'll see. --rich ________________________________ - CONFIDENTIAL- This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email. ```