# Re: Invalid copy source path

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 5 Dec 2011 11:30:36 +0100

On Thu, Dec 01, 2011 at 01:38:14PM -0500, Michael.Orozco_at_fluor.com wrote:
> I am working in a windows server 2003 environment. I would much rather be
> in a linux environment, but that is neither here nor there.
>
> I have a very large repository that I am trying to seperate out into
> individual repositories. Some are small, and others large.
>
> I have tried a lot of different options, but so far, I am having lots of
> trouble. Here is the error message I receive.
>
> svndumpfilter: Invalid copy source path
> '/MAXIMO/releases/release-next/scripts/pre-configdb/SR04592-configdb.sql'
>
> I created a dump file, and then I tried to seperate out the programs from
> dump file. Like so:
>
> svndumpfilter.exe include MAXIMO --drop-empty-revs --renumber-revs
> --preserve-revprops < F:\repo_all.dmp > D:\repo_maximo.dmp
>
> Problem I encountered is I keep getting the Invalid copy source path
> error. I get about 6, or 7 errors.
>
> I tried a few like:
>
> svndumpfilter.exe exclude --drop-empty-revs --renumber-revs
> /MAXIMO/BizTalk/Final_BizTalk_Maximo_Matman "/MAXIMO/BizTalk/Splittin_in_3
> files"
> /MAXIMO/releases/archive/release-20100628/scripts/pre-configdb/SR04592-configdb.sql
> /MAXIMO/releases/release-next/scripts/pre-configdb/SR04592-configdb.sql
> /MAXIMO/releases/release-next/scripts/revert/SR04592-revert-configdb.sql
> D:\repos\repo_exclude.dmp
>
> It seemed to be working. But I get to
> /MAXIMO/releases/archive/release-20100628/scripts/pre-configdb/SR04592-configdb.sql
> and I get the same error message.
>
> I found the file, and committed it into that directory. It was not there
> before, and gave me the same error. It doesn't give me any other infor
> except for that. Is there anything I can do for this?
>
> I would much rather delete that file, and just go on without it, but it
> seems subversion will not let me do that!

You have to include copy sources of files you want to keep.
The reason is that it is often impossible to reconstruct the file