Ben Collins-Sussman wrote:
> 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.
It's actually quite easy to fix. I have a patch to do that in my tree,
and I plan to send it to the list for review after I've cleaned it up a bit.
Note that there are two problems. The first one is that svnserve does
not "relay" any errors from the open_repos call. The second one is that
we do not have an error code to use when BDB returns EACCESS. My fix
adresses both these issues.
I'll be back! ;-)
/Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 18:48:20 2003