What are semantics of "Node-action: replace"

[Charles Butterfield <ch...@nextcentury.com>]

While struggling with other issues noted on this list (see aside at
end), I started looking at the svn dump format and have a couple of
questions

1) When is node-action "replace" used and what are the implications
thereof?  Is it simply used instead of "add" when the indicated path
already exists (presumably via "svn move" or "svn copy")?  Or is it ever
used instead of a "change" action?  For that matter, would anything go
wrong if "change" were used instead of replace?

2) Is there any documentation on the dump file format with more
extensive discourse that the document "dump-load-format.txt"?  Or
alternatively, is there other design documentation that discusses the
details of the various node-actions?

ASIDE - What is motivating this is trying to understand how hard it
would be to hack up a dump file to address some of the problems
encountered in deleting old history, an in:

	svnadmin dump repo -r2000:9999 | svnadmin load virgin-repo

which complains if any of revs 2000-9999 were copied from revs prior to
2000.

Thanks for any insight,
-- Charlie

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Svnadmin Load utility

[Kevin Grover <ke...@kevingrover.net>]

On Thu, Feb 21, 2008 at 11:58 AM, Patwardhan, Rajesh <
rajesh.patwardhan@etrade.com> wrote:

> Is there a limit on the extent of data that the svnadmin load utility
> can take as input stream?
>
> We have a 10 G export and are facing some challenges with smaller files
> due to problems being discussed on another thread
>
> "svnadmin dump generates (hopefully) spurious warnings - Loading this
> dump into an empty repository will fail"
>
> When I had initially tried with 1 huge file it had failed ..
>
> Then without realizing that error mentioned above can occur we tried
> smaller dumps and those failed too
>
> So now we are back to exploring a huge file and wondering if there is
> constraint from svn load utility or is just some restrictions coming
> from the OS ..
>
> If someone has experienced this or can give a pointer in the right
> direction, that would be really helpful.
>
> Thank you very much in advance for your time.
>
> Regards,
> Rajesh
>
>
If I understand your post, you can dump the repo to one file, but you can't
load it back in.

Is that correct?  If so, what are the OS (source and destination, and
filesystems) and svn version numbers?

Also, what command(s) did you try and what errors/problems did you
encounter?

I can't imagine there being a limit from SVN.  A possible problem that comes
to mind:
1) Are any revisions close to or over the file size limit for the
destination OS?
On the source machine, cd into the repository directory, then cd into
db/revs (db\revs) and look at the sizes of the files.  If any are too large
for the destination OS/filesystem, you will have problems loading the
repository dump (on that OS/filesystem).

Svnadmin Load utility

["Patwardhan, Rajesh" <ra...@etrade.com>]

Is there a limit on the extent of data that the svnadmin load utility
can take as input stream?

We have a 10 G export and are facing some challenges with smaller files
due to problems being discussed on another thread 	

"svnadmin dump generates (hopefully) spurious warnings - Loading this
dump into an empty repository will fail" 

When I had initially tried with 1 huge file it had failed .. 

Then without realizing that error mentioned above can occur we tried
smaller dumps and those failed too 

So now we are back to exploring a huge file and wondering if there is
constraint from svn load utility or is just some restrictions coming
from the OS ..

If someone has experienced this or can give a pointer in the right
direction, that would be really helpful.

Thank you very much in advance for your time.

Regards,
Rajesh 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: What are semantics of "Node-action: replace"

[Blair Zajac <bl...@orcaware.com>]

Not related to your question, but please do not reply all to start a new thread. 
  See here why:

http://subversion.tigris.org/mailing-list-guidelines.html#fresh-post

Thanks,
Blair

Charles Butterfield wrote:
> While struggling with other issues noted on this list (see aside at
> end), I started looking at the svn dump format and have a couple of
> questions
> 
> 1) When is node-action "replace" used and what are the implications
> thereof?  Is it simply used instead of "add" when the indicated path
> already exists (presumably via "svn move" or "svn copy")?  Or is it ever
> used instead of a "change" action?  For that matter, would anything go
> wrong if "change" were used instead of replace?
> 
> 2) Is there any documentation on the dump file format with more
> extensive discourse that the document "dump-load-format.txt"?  Or
> alternatively, is there other design documentation that discusses the
> details of the various node-actions?
> 
> ASIDE - What is motivating this is trying to understand how hard it
> would be to hack up a dump file to address some of the problems
> encountered in deleting old history, an in:
> 
> 	svnadmin dump repo -r2000:9999 | svnadmin load virgin-repo
> 
> which complains if any of revs 2000-9999 were copied from revs prior to
> 2000.
> 
> Thanks for any insight,
> -- Charlie
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org