Re: Berkeley DB error...

On Mon, Sep 27, 2004 at 10:00:44AM -0500, Bennett,Dustin wrote:
>
> Thanks for the reply! Honestly, I am very new to svn and not too
> familiar with it. I simply followed instructions to setup a
> repository for some developers that I support and pointed them to it.
> How do you know that we are overlaying a repository and a working
> copy in the same directory?

The fact that when you run "svn status" the files listed as unknown
(those with a ?) bare the same names as those that make up the actual
repository.

This is what I get running "svn status" from within the directory
containig my test respository:

/var/lib/svn/test$ svn status
svn: '.' is not a working copy

And you can see from the output of find that your listing contains many
of the same files and directories

/var/lib/svn/test$ find
.
./dav
./locks
./locks/db.lock
./locks/db-logs.lock
./hooks
./hooks/start-commit.tmpl
./hooks/pre-commit.tmpl
./hooks/pre-revprop-change.tmpl
./hooks/post-commit.tmpl
./hooks/post-revprop-change.tmpl
./conf
./conf/svnserve.conf
./README.txt
./format
./db
./db/DB_CONFIG
./db/__db.001
./db/__db.002
./db/__db.003
./db/__db.004
./db/__db.005
./db/log.0000000007
./db/nodes
./db/revisions
./db/transactions
./db/copies
./db/changes
./db/representations
./db/strings
./db/uuids
./db/log.0000000006

> Is it possible that this is what caused svn to generate the
> DB fatal error?

No idea. But you should avoid doing so.

-- 
Jamin W. Collins
Remember, root always has a loaded gun.  Don't run around with it unless
you absolutely need it. -- Vineet Kumar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org