svnadmin recover and setlog curiosities

Is it kosher for "svnadmin recover" to modify DB permissions? Trac
started throwing up permission errors, apparently because group write
access is stripped from the "__db.xxx" files after I run recover.

I ran recover the first time after being told to do so while attempting
to run "svnadmin setlog":

$ svnadmin setlog /Library/svnrepo/ -r 204 newlogfile
svn: Berkeley DB error while opening environment for filesystem
/Library/svnrepo/db:
DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: PANIC: fatal region error detected; run recovery

I can't repeat that, so I don't have any real reason to think that
setlog caused the DB problem. However, I can repeat the unrelated
problem that cropped up when I tried to run setlog again:

$ svnadmin setlog /Library/svnrepo/ -r204 newlogfile
svn: Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook

I'm the administrator, and I don't need any hooks at this point, so I
haven't set any up. Running setlog a third time with "--bypass-hooks"
works successfully, but if I don't include that argument, setlog
consistently fails with the above error.

I'm using 1.1.0rc2 on Mac OS X 10.3.5.

Thanks,

  -nat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 19 19:42:47 2004