[svk-users] Crash on 'svk sync'

[John Resig]

Hey Everyone -

We've been finding svk to be immensely useful over at the jQuery
project. Unfortunatley, we hit a snag today, during our normal sync
from Google Code.

$ svk sync //
Syncing http://jqueryjs.googlecode.com/svn
Retrieving log information from 2721 to 2722
        (in cleanup) Svndiff data ends unexpectedly: Unexpected end of
svndiff input
Incomplete data: Delta source ended unexpectedly
        (in cleanup) Svndiff data ends unexpectedly: Unexpected end of
svndiff input
*** glibc detected *** double free or corruption (!prev): 0x09724d70 ***
Abort

Here's the version information:

$ svk -v
This is svk, version v2.0.1 (using Subversion bindings 1.4.3)
$ svn --version
svn, version 1.4.3 (r23084)
   compiled Jan 25 2007, 18:41:18
[snip]

And the diff in question isn't even particularly interesting:

$ svn diff -r 2721 .
Index: trunk/plugins/tablesorter/2.0/docs/index.html
===================================================================
--- trunk/plugins/tablesorter/2.0/docs/index.html       (revision 2721)
+++ trunk/plugins/tablesorter/2.0/docs/index.html       (working copy)
@@ -469,9 +469,9 @@
        <p><strong>It's free right?</strong></p>

        <p>Yes, it's dual licensed under <a class="external"
href="http://www.opensource.org/licenses/mit-license.php">MIT</a>
-    and <a class="external"
href="http://www.opensource.org/licenses/gpl-license.php">GPL</a>
licenses. So you can basicly do what every you whant with it (Copy,
Modify and even sell it).</p>
+    and <a class="external"
href="http://www.opensource.org/licenses/gpl-license.php">GPL</a>
licenses. So you can do whatever you want with it even sell it.</p>

-       <p>If you like tablesorter and fell like it. A small donation
is always appreciated.</p>
+       <p>If you like tablesorter or just fell like it. A small
donation is always appreciated.</p>

        <p>
        <form action="https://www.paypal.com/cgi-bin/webscr"
method="post" id="donate">



Is there a version issue at play here? Or is this something that I
should file a bug on?

--John