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

[Peter Samuelson]

[Ross Boylan]
> Instead, how about this?

Sounds good, I just made minor adjustments at the end.

> > -'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.
> 
> It may not be sufficient, because if they haven't done so they probably
> need to change settings for all the files, not just those in conf and
> hooks.

Right, the wording is unclear, I meant chown/chmod for the whole
repository but I can see why you'd read it as just the config files.

> Perhaps advising 'cp -a' would help, though I suspect that if you
> aren't the appropriate user, or possessed of appropriate permissions,
> you can't preserve owner/group.

Won't work for that last paragraph, it's describing how to reload your
repo from scratch.

Peter

--- README.db4.3
+++ README.db4.3
@@ -38,6 +38,13 @@
 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".
 
+Note the ownership and permissions of your existing repository files
+(e.g. with 'ls -l').  The conversion utilities make no effort to
+preserve ownership and permission, so you should su to the appropriate
+user.  If the files are group-writable, set 'umask 002'.  Alternately,
+you can use 'chown -R' and 'chmod -R' to set things right after the
+conversion.
+
 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 +88,8 @@
   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
-verifying that everything went well, you can remove /srv/svn/repo1.old
-and rename /srv/svn/repo1.new to /srv/svn/repo1.
+'hooks' directories into the new copy of the repository, and use
+'chown' and 'chmod' to ensure that the permissions for the whole
+repository are the same as what you had before.  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/67e849f3/attachment.pgp