svn lock frustrations

Again with the technical geeky posts I know it's been a long time.

Every week or so, someone from my team decides to run an SVN update on staging using root. I don't know why, I don't care. Short of actually just deleting the folder, and checking out a fresh copy, here is what I do to fix it all:

The error:
svn: Can't open file 'PATH/TO/YOUR/FILES/.svn/lock': Permission denied

The solution:
cd /PATH/TO/MY/PROJECT
sudo find . -exec chown apache:development {} \;
sudo find . -exec chmod 2770 {} \;
svn cleanup

Usually I'll login as root to do the first three steps, then go back to my user to run the cleanup and updates.

LOL to people who don't like this solution, if it doesn't work for you? keep looking. Posting comments complaining isn't going to help.

BFN.