just after making my repository work again, guess what, I got the same error
once again when doing an update. Following two links in the FAQ I luckily
ended up at the end of http://svnbook.red-bean.com/en/1.0/ch06s05.html which
told me about "umask 002" and "chmod g+s". This is indeed the cause of my
I guess, http://svn.haxx.se/dev/archive-2004-10/0966.shtml sums up the problem
pretty nicely: "This experience detracts from the perception of svn as it
results in 'hangs' which need 'database recovery'."
That post is six months old, so I'm wondering why I'm still being bitten by
this bug. Assuming that a fix (or workaround) is REALLY hard, how about
adding this info (which I had to find the hard way) to the FAQ?
Further, the solution to the umask problem pointed out in
http://svnbook.red-bean.com/en/1.0/ch06s05.html doesn't really help me
because it's a major hassle to make all users of my repository setup a
wrapper around svnserve (no, I don't have root on that box).
Received on Mon May 9 10:45:57 2005
- application/pgp-signature attachment: stored