[Ross Boylan] > Apparently svnadmin recover must be run as an appropriate user, not > root. I ran it as root and things stopped working.
Actually, you've run into a more general problem: when using BDB-format repositories, the BDB backend makes no effort to manage the ownership _or_ permissions of the files it writes to. If you run it as root, it will create files owned by root. If you run it with umask 022, it will create files that are not group-writable, even if the rest of the repository is. The FSFS backend has the same problem with file ownership (indeed, if you are not the root user, you generally can't create files owned by anyone else anyway), but it does manage permission bits properly. In addition, the FSFS backend, unlike the BDB backend, does not create or write any files when you do read-only operations. Conclusion: if you use BDB-format repositories, ownership of files in the repositories will depend on the user you access them as, even for read-only access, and permission bits will depend on the current umask. This is well-known and I don't think there's much we can do about it, but perhaps it could be documented more clearly. I'll continue to think about where it might be appropriate to document it. (It isn't really NEWS, as it has been true of all the binaries in Subversion since the beginning of time.) > Also, the NEWS file was not displayed or emailed to me by > apt-listchanges. I don't know why; I've seen this problem with other > packages because of subtle formatting issues with NEWS.Debian. > Perhaps the lack of a "*" before the news item makes a difference? Hmmm. I don't use apt-listchanges (bad Peter!) so I hadn't tested this. I'll have a look. Thanks, -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
signature.asc
Description: Digital signature
