Guido van Rossum <guido@python.org> writes:
> Request to the svnserve developers: try to distinguish between
> permission problems on the repository and "no repository found".
This is a common problem, many have complained. I'm not sure how to
fix it, though. Ultimately it's BerkeleyDB that throws an error, and
I think it's pretty vague -- like "hey, I couldn't open the db
environment." BerkeleyDB never says *why* it couldn't open the
environment (permission problem? is it not there? etc.) So
Subversion is just relaying the same vague message back to the user.
I wonder if we can make this situation better, somehow.
> But then ANOTHER issue came up, once the second developer used ssh
> tunneling: THE <repos>/db DIRECTORY NEEDS TO HAVE THE SETGID BIT SET!
> (I don't know about other directories under <repos>, or <repos>
> itself.) Without this, files created by user x will have owner and
> group set to x, and that defeats the group writability for other
> members of the subversion group. (Our setup lets everyone log in via
> ssh as themselves, and has a separate subversion group that you must
> be in before you can use svnserve. The subversion group is nobody's
> primary group.)
I'll make a note to add this to the appropriate place in the book,
where it discusses creating a umask wrapper around svnserve.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 17:12:03 2003