[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnrdump produce a strange dump file

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Thu, 1 Oct 2015 09:29:28 -0400

On Thu, Oct 1, 2015 at 4:19 AM, Yves Martin <ymartin1040_at_gmail.com> wrote:
> Hello,
> I have a Subversion 1.6.17 server running on Debian Linux and access through
> I used both Subversion 1.8.10 and Subversion 1.9.2 to produce a partial dump
> of the repository:

*Why*? If you have a subversion 1.6.17 server, why wouldn't you use
the the local svnadmin dump command for maximum binary compatibility?
I'm not saying it shouldn't work, just wondering why you're even

If you're doing an rsync or scp to a remote system and doing the
svndump there, you're running the risk of transferring content in the
middle of an atomic operation and thus confusing the system.

> svnrdump dump -r 51686:77787
> https://myhost/subversion/repository/PROJECT/trunk/amodule | gzip >
> amodule.dump.gz

Does anyone actually use "svnrdump"? I've not explored it myself, but
don't see where it's a big advantage over a remote "ssh hostname
svnadmin dump" command, which avoids the kind of confusion I just
described. I'd start there, to avoid certain levels of uncertainty and
incompatibility with an out of date and no longer supported Subversion
release with a more modern tool that may not have been thoroughly
tested with it.
Received on 2015-10-01 15:29:34 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.