Subversion 1.7 and 1.8

[Jim Jagielski]

You need to downgrade to subversion 1.7 and force git-core to not require
"the latest".

You also need to watch the perl-bindings as well, and make sure they are
against 1.7 and not 1.8


On Sat, Aug 3, 2013 at 5:20 PM, Adam Mercer <ram at macports.org> wrote:

> On Sat, Aug 3, 2013 at 9:50 AM, Jim Jagielski <jimjag at gmail.com> wrote:
> > On Aug 2, 2013, at 10:30 PM, Adam Mercer <ramercer at gmail.com> wrote:
> >
> >> I'm assuming this unreliability with subversion-1.8 and git-svn is the
> >> reason for this:
> >>
> >> $ git svn clone -s -r90000:HEAD
> >> https://svn.macports.org/repository/macports/trunk/dports
> >> Initialized empty Git repository in /Users/ram/macports/dports/.git/
> >> Using higher level of URL:
> >> https://svn.macports.org/repository/macports/trunk/dports =>
> >> https://svn.macports.org/repository/macports
> >> perl5.12(6874) malloc: *** error for object 0x7fed70e2ae00: pointer
> >> being freed was not allocated
> >> *** set a breakpoint in malloc_error_break to debug
> >> error: git-svn died of signal 6
> >
> > Yeppers.
>
> Well I guess my development is going to be on hold for a while then...
>
> Cheers
>
> Adam
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20130804/db581c7a/attachment-0001.html>