Davide Canalia wrote:
>>Maybe it will be worth trying dump repository "per partes". So if your
>>rep. has about 4GB and let's say about 20000 revisions, you can dump for
>>the first time only first 5000 revisions, if you succeed try next 5000
>>revisions and so on. Hope it can help a bit.
>>
>>
>
>Well i get the same error also with repository with only 1 commit...
>So I don't think it can works.. however can you exaplain me how can I do
>that?
>
>
>
>Obsah teto zasilky byl zkontrolovan na pritomnost viru technologii BitDefender
>Odeslano 602Pro LAN SUITE - http://www.software602.cz/
>
>
>
>
See svn documentation for full explanation of migrating repository. Here
is a small piece of it:
...
However, you can change this default behavior. If you add the
--incremental option when you dump your repository, svnadmin will
compare the first dumped revision against the previous revision in the
repository, the same way it treats every other revision that gets
dumped. It will then output the first revision exactly as it does the
rest of the revisions in the dump range—mentioning only the changes that
occurred in that revision. The benefit of this is that you can create
several small dump files that can be loaded in succession, instead of
one large one, like so:
$ svnadmin dump myrepos --revision 0:1000 > dumpfile1
$ svnadmin dump myrepos --revision 1001:2000 --incremental > dumpfile2
$ svnadmin dump myrepos --revision 2001:3000 --incremental > dumpfile3
These dump files could be loaded into a new repository with the
following command sequence:
$ svnadmin load newrepos < dumpfile1
$ svnadmin load newrepos < dumpfile2
$ svnadmin load newrepos < dumpfile3
...
This is what I ment. I had the same problem once but it was permission
issue.
--
Smrk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 27 11:17:24 2005