1 In poking around at the svn backend I found that the svn post-commit
2 hook calls to svn update fail regularly with an error code of 256.
3 Apparently during the post-commit hook can't update because the
4 working copy is locked from the commit. Since the post-commit hook doesn't send
5 errors anywhere and svn update runs with --quiet anyhow, this error
6 isn't usually visible, but on my system:
8 ethan@sundance:~/tests/webtemplates/ikiwiki3/wc$ svn commit -m "Blah.."
10 Transmitting file data .
13 #verifying output was created
14 ethan@sundance:~/tests/webtemplates/ikiwiki3/wc$ less ../dest/index.html
16 ethan@sundance:~/tests/webtemplates/ikiwiki3/wc$ svn info
18 URL: file:///home/ethan/tests/webtemplates/ikiwiki3/svn/trunk
19 Repository Root: file:///home/ethan/tests/webtemplates/ikiwiki3/svn
20 Repository UUID: f42bb0d6-3c1e-0410-b2d4-aeaad48dd6c4
24 Last Changed Author: ethan
26 Last Changed Date: 2006-09-24 21:15:55 -0400 (Sun, 24 Sep 2006)
28 A sample error message (obtained through file redirection) is:
30 svn: Working copy '.' locked
31 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
33 Did I do something stupid again or is this the case on your system too?
36 Additional note: this doesn't happen when performing svn commits from another wc,
37 but *does* happen when committing from the web.