John Yeates wrote:
> On 15/02/05 11:44 , SteveKing wrote:
>> You have to use the 'svnadmin' command from the same version you've
>> created the repository with. Otherwise the dump won't work. So if you
>> used TSVN1.1.3 for example, then you have to use Subversion 1.1.3 to
>> dump the repository (the version TSVN1.1.3 is linked against).
>
> Yes, both are 1.1.3. The problem seems to be that the original was
> just being used locally - ie work on file, check in and the revision
> data goes in a .svn subdirectory. svnadmin appears to be looking for
> the revision data to be stored in a single db rather than a bunch of
> .svn subdirectories :(
NoNoNo! The .svn directories are in your working copy. They do *not*
store the history at all. The repository is in a completely separate
folder. If you right click on your WC root and check the subversion
properties it will show the URL of the repository, ie. where it is on
your local machine.
A repository has the structure:
RepositoryFolder/
conf/
dav/
db/
hooks/
locks/
format
README.txt
If you want to move it to a server you should dump/load as described in
the SVN book. You can do a naive copy, but only if the client you use
now and the server you plan to use are running the same OS type, same
repo access software, same version of BDB (if it's a BDB repo), etc.
Much safer to dump/load.
That also implies that you are backing up your WC and not the
repository. If you care about your data then you really must back up the
repository. Use the svnadmin hotcopy command to make a back-up-able
copy.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Feb 15 13:35:14 2005