Bug#345819: subversion: README.db4.3 needs to cover ownership issues

[Peter Samuelson]

[Ross Boylan]
> Minimally, the instructions could just say to be aware of ownership
> and permission issues.  I know that's pretty obvious, but I managed
> to miss it :)

I think I would have missed it too!  Here is what I've put in for the
next upload - let me know if you think it's still insufficient.

Thanks,
Peter

--- README.db4.3
+++ README.db4.3
@@ -38,6 +38,11 @@
 can't use "svnadmin", since it won't read BDB 4.2 environments.  You
 can use "cp", though, e.g. "cp -a /srv/svn/repo1 /srv/svn/repo1.bak".
 
+Ensure that new files created will be writable by your repository
+users: If your repository is single-user, use 'su username' if needed.
+If it's group-writable, use 'umask 002'.  The utilities do not go to
+any special effort to preserve existing permissions on the DB files.
+
 Next, make sure the repository databases are in a consistent state
 (normally they will be, but you are about to destroy the data needed to
 fix them if they aren't):
@@ -81,6 +86,7 @@
   svnadmin dump -q /srv/svn/repo1.old | svnadmin load -q /srv/svn/repo1.new
 
 You will also need to copy any customisations from the 'conf' and
-'hooks' directories into the new copy of the repository.  Then, after
+'hooks' directories into the new copy of the repository, and use
+'chown' and 'chmod' to make the access permissions match.  Then, after
 verifying that everything went well, you can remove /srv/svn/repo1.old
 and rename /srv/svn/repo1.new to /srv/svn/repo1.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/attachments/20060104/28369e15/attachment.pgp