Aleksandr Sidorenko <asidore...@cashontime.com> writes:
> The sqlite command worked (I see the expected output), but I suspect that's
> because the rep-cache.db file was already there (since 1.6.12). If I move it,
> though, the file is NOT recreated.
>
> greping through /proc/xxx/maps gives me the following:
>
> 2a96fc4000-2a97058000 r-xp 00000000 08:01 18104376
> /usr/local/lib/libsqlite3.so.0.8.6
> 2a97058000-2a97158000 ---p 00094000 08:01 18104376
> /usr/local/lib/libsqlite3.so.0.8.6
> 2a97158000-2a9715c000 rw-p 00094000 08:01 18104376
> /usr/local/lib/libsqlite3.so.0.8.6
>
> sqlite was built with default options, but "--enable-threadsafe" defaults to
> "yes" if it's not used, so I guess it *is* built with thread support?
Try this patch:
Index: subversion/libsvn_fs_fs/fs_fs.c
===================================================================
--- subversion/libsvn_fs_fs/fs_fs.c (revision 1202738)
+++ subversion/libsvn_fs_fs/fs_fs.c (working copy)
@@ -5580,6 +5580,7 @@
svn_error_t *err;
err = svn_fs_fs__get_rep_reference(&old_rep, b->fs, rep->sha1_checksum,
b->parent_pool);
+ SVN_ERR(err);
/* ### Other error codes that we shouldn't mask out? */
if (err == SVN_NO_ERROR
|| err->apr_err == SVN_ERR_FS_CORRUPT
To make the first error hard. Then try committing a file over ra_local:
$ rm -rf repo && svnadmin create repo
$ svn import -mm repo/format file://`pwd`/repo/f
That should make the error explicit.
--
Philip
