> > So I expect that you *can* distinguish between (paraphrasing) "no
> > database there" and "no permission to open that database" from the
> > BerkeleyDB error code. In that case I would recommend passing the
> > most specific error (anything else than "no database there") back to
> > the client. You could also try to detect the repository through
> > different means, e.g. looking for something that has a subdirectory
> > named "db", and only trying the BerkeleyDB open call if that is
> > found.
>
> There was actually a patch committed (yesterday?) to do just this.
> Previously the error was not being propagated back up to the client.
>
> In the future, errors like this should produce output like this:
>
> svn: Couldn't find a repository
> svn: No repository found in 'svn://localhost/home/svn/trunk'
> svn: Berkeley DB error
> svn: Berkeley DB error while opening environment for filesystem
> /home/svn/db: Permission denied
>
> (Well, according the the submitter's post to the list it should, I
> haven't actually tested it because I don't have a current version of svn
> built at the moment.)
Cool. I'll see if I can install just the svnserve binary built from
the latest source -- I still haven't figured out why svn built from
source core dumps for me (nor even how to actually get a core dump, or
where the core gets dumped).
--Guido van Rossum (home page: http://www.python.org/~guido/)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 25 04:53:18 2003