From: Eric Wong <e@80x24.org>
To: K Richard Pixley <cnp637@zebra.com>
Cc: git@vger.kernel.org
Subject: Re: Problems with "git svn clone"
Date: Thu, 20 Oct 2016 00:49:56 +0000 [thread overview]
Message-ID: <20161020004956.GA8083@starla> (raw)
In-Reply-To: <dea3ab60-be6b-ebcc-1047-6ab28a25979b@zebra.com>
K Richard Pixley <cnp637@zebra.com> wrote:
> On 10/19/16 13:41 , Eric Wong wrote:
> >K Richard Pixley <cnp637@zebra.com> 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
next prev parent reply other threads:[~2016-10-20 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 21:03 Problems with "git svn clone" K Richard Pixley
2016-10-19 20:41 ` Eric Wong
2016-10-19 20:49 ` K Richard Pixley
2016-10-20 0:49 ` Eric Wong [this message]
2016-10-21 16:33 ` K Richard Pixley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161020004956.GA8083@starla \
--to=e@80x24.org \
--cc=cnp637@zebra.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.