Hi,
I think that these question is not for me, but to the development staff.
But as a user, if I got a message like these, certainly that I will look
at my NFS server first, instead the of the SVN.
Att.
Celso Suzuki
Em 21-02-2013 10:46, Stefan Sperling escreveu:
> On Thu, Feb 21, 2013 at 09:47:34AM -0300, Celso Tadao Suzuki wrote:
>> Hi,
>>
>> Yes, you are right again.
>> I ran the nfslock service and the svn is working fine now.
>>
>> Thank you for your attencion.
>>
> Perhaps we should apply a patch like this?
> (I haven't run the tests on it yet.)
>
>
> [[[
> * subversion/svn/svn.c
> (sub_main): Advise users about possible causes of SVN_ERR_SQLITE_BUSY.
> ]]]
>
> Index: subversion/svn/svn.c
> ===================================================================
> --- subversion/svn/svn.c (revision 1448349)
> +++ subversion/svn/svn.c (working copy)
> @@ -2829,6 +2829,18 @@ sub_main(int argc, const char *argv[], apr_pool_t
> "(type 'svn help cleanup' for details)"));
> }
>
> + if (err->apr_err == SVN_ERR_SQLITE_BUSY)
> + {
> + err = svn_error_quick_wrap(err,
> + _("Another process is blocking the "
> + "working copy database, or the "
> + "underlying filesystem does not "
> + "support file locking; if the working "
> + "copy is on a network filesystem, make "
> + "sure file locking has been enabled "
> + "on the file server"));
> + }
> +
> return EXIT_ERROR(err);
> }
> else
>
> .
>
Received on 2013-02-21 15:22:08 CET