On Fri, Oct 2, 2015 at 3:26 AM, Yves Martin wrote:
> Hello,
>
> The problem I face now when using "svnadmin dump" is "svndumpfilter:
> E23: Invalid copy source path' when selecting the three /trunk modules I
> am interested in.
> Such a problem "svnrdump" does not produce.
>
> Thank you in ad
Hello,
The problem I face now when using "svnadmin dump" is "svndumpfilter:
E23: Invalid copy source path' when selecting the three /trunk modules
I am interested in.
Such a problem "svnrdump" does not produce.
Thank you in advance for your help
--
Yves Martin
On Thu, 2015-10-01 at 09:29 -0400, Nico Kadel-Garcia wrote:
> 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
On Oct 1, 2015, at 8:29, Nico Kadel-Garcia wrote:
>
> On Thu, Oct 1, 2015 at 4:19 AM, Yves Martin wrote:
>> Hello,
>>
>> I have a Subversion 1.6.17 server running on Debian Linux and access through
>> HTTPS.
>>
>> I used both Subversion 1.8.10 and Subversion 1.9.2 to produce a partial dump
>>
On Thu, Oct 1, 2015 at 4:19 AM, Yves Martin wrote:
> Hello,
>
> I have a Subversion 1.6.17 server running on Debian Linux and access through
> HTTPS.
>
> 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 serv
Yves Martin writes:
> I got a version 3 dump which has the following trouble: almost all files
> content begins with a strange "SVN" binary sequence.
That's normal: dump is a binary format and that is the start of some
data in svndiff format.
> As a result, load operation fails as Text-content-
Hello,
I have a Subversion 1.6.17 server running on Debian Linux and access
through HTTPS.
I used both Subversion 1.8.10 and Subversion 1.9.2 to produce a partial
dump of the repository:
svnrdump dump -r 51686:77787
https://myhost/subversion/repository/PROJECT/trunk/amodule | gzip >
amodule.du
