Aleksandr Sidorenko <asidore...@cashontime.com> writes: > On 2011-11-16, at 11:15 , Philip Martin wrote: > >>> ... >> >> 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. > > I should note that the error does NOT occur locally, or if I use svnserve. It > only occurs for commits done via HTTP (the mod_dav_svn module). > > For local commits (or via svnserve), the repo/db/rep-cache.db file is touched > as expected (the modification date changes).
That should work for apache as well, but only the first commit after apache is started. Subsequent commits will just give the atomic error message. -- Philip
