--- Comment #1 from Tim Starling <> 2011-02-07 23:40:14 
UTC ---
I'm not exactly sure why this happens. But Subversion's locking system is
probably broken due to the fact that the working copy is on NFS. So one
possibility is that the svn up from the cron job runs at the same time as the
svn up from xinetd, and that this breaks the working copy. 

The solution is to make ExtensionDistributor not use NFS, which is desired
anyway for operations reasons. Also the use of xinet was probably not ideal
since it is the only thing in the cluster that uses it. It would be better if
it were rewritten to do everything using internal web services. A web service
could provide a frontend to a tarball storage system and Subversion proxy.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to