When I committed r992004, "svn" reported that the commit failed, but in
fact it succeeded on the server.  The command and output were:

[[[
$ svn ci -m "* subversion/libsvn_wc/tree_conflicts.c^M  
(svn_wc__write_tree_conflicts): Remove an obsolete comment." 
subversion/libsvn_wc/tree_conflicts.c
Sending        subversion/libsvn_wc/tree_conflicts.c
Transmitting file data 
./home/julianfoad/src/subversion-a/subversion/svn/commit-cmd.c:141: 
(apr_err=200030)
/home/julianfoad/src/subversion-a/subversion/libsvn_client/commit.c:847: 
(apr_err=200030)
svn: Commit failed (details follow):
/home/julianfoad/src/subversion-a/subversion/libsvn_ra_neon/commit.c:1356: 
(apr_err=200030)
/home/julianfoad/src/subversion-a/subversion/libsvn_ra_neon/merge.c:762: 
(apr_err=200030)
/home/julianfoad/src/subversion-a/subversion/libsvn_ra_neon/util.c:1298: 
(apr_err=200030)
/home/julianfoad/src/subversion-a/subversion/libsvn_ra_neon/util.c:1539: 
(apr_err=200030)
/home/julianfoad/src/subversion-a/subversion/libsvn_ra_neon/util.c:765: 
(apr_err=200030)
svn: database is locked
]]]

The "svn" used is trunk r991940M.  (The local mod is an optimised
version of svn_txdelta_apply_instructions().)  Using Neon 0.28.6.  The
repos root URL being used (as shown by svn info) is
<https://svn.apache.org/repos/asf>.

This looks like a server-side bug.  Any insight?

- Julian


Reply via email to