more subversion

[Robert Huff]

	On one of my systems, running:

FreeBSD 13.0-CURRENT #0 r354131: Mon Oct 28 17:27:33 EDT 2019  amd64

	the src, ports, and doc code bases are updated overnight.  This
has worked without problem for years ...
	... until about ten days ago when I started getting:
	
Updating src ...
svn: E200033: 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
svn: E200033: sqlite[S5]: database is locked
svn: E200042: Additional errors:
svn: E200033: sqlite[S5]: database is locked
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
svn: E155004: Working copy '/usr/src' locked.
svn: E155004: '/usr/src' is already locked.
.. done.
Updating ports ...
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
svn: E155004: Working copy '/usr/ports' locked.
svn: E155004: '/usr/ports' is already locked.
.. done.
Updating docs ...
Updating '.':
Skipped 'it_IT.ISO8859-15/articles' -- Node remains in conflict

	The filesystem is UFS2, entirely local.
	So I cd to each {src, ports, doc}; run "svn cleanup" as directed
and am told it worked:

root at jerusalem> cd /usr/src	
root at jerusalem> svn cleanup
root at jerusalem>

	and yet the next day ... it's ba-a-a-a-a-a-ck!
	Obviously not the subversion guru.  What's wrong?  And how do I
fix it?  (Fixing now; recriminations - if necessary - later.)


			Respectfully,


				Robert Huff