svndumpfilter question

[po...@yahoo.com]

> 
> Hi,
> 
> I am trying to filter an svn dump to get only one module (ModuleA)  from
> the repository. A simplistic representation of the  repository is as
> follows  -
> 
> trunk ---
>    --- ModuleA
>    --- ModuleB
>    --- ModuleC
>    --- ModuleD
> 
> tags ----
>     --- ModuleATag1.1
>     --- ModuleATag1.2
>     --- ModuleATag2.0
>     ...............
>     --- ModuleBTagx.x
>    ...........
> 
> 
> 
> I'm interested in getting /trunk/ModuleA  and all  /tags/ModuleATagx.x
> The svndumpfilter works fine for the trunk folder using the
> svndumpfilter include command. However,  for the tags it runs into a
> problem. The issue is that  the repo has been tagged by copying at the
> root level. So /tags/ModuleATagx.x have been created by copying /trunk.
> Therefore /tags/ModuleATagx.x  have the following structure 
> 
> /tags/ModuleATagx.x -----
>     ----ModuleA
>     ----ModuleB
>     ----ModuleC
>     ......
> 
> Implying all tags contain the entire folder structure. 
> 
> 
> My question is as follows - Is there anyway that I can filter the dump
> so as to get only /tags/ModuleATagx.x/ModuleA?
> 
> Since the tags were created by copying at the root level,  if I specify
> the /tags/ModuleATagx.x/ModuleA to be included in the svnfilter dump
> command,  I do not get anything. If I try to get the complete tag i.e.
> /tags/ModuleATagx.x, I get an error since it needs the entire trunk.  I
> tried using svndumpfilter2 and svndumpfilter3,  to get the complete tags
> i.e. /tags/ModuleATagx.x, but did not get much joy. They run too slowly
> and hang in the initial stages. 
> 
> This is a big repository with quite a few moves, so the above is not the
> only issue that I am facing. However, I am able to get around the other
> issues by some workarounds - like including some extra folders or  by
> splitting the dump into revisions and hand selecting the ones to load. 
> 
> Regards
> 

RE: svndumpfilter question

["Cooke, Mark" <ma...@siemens.com>]

> -----Original Message-----
> From: poonamah@yahoo.com [mailto:poonamah@yahoo.com] 
> Sent: 27 May 2011 11:13
> To: users@subversion.apache.org
> Subject: svndumpfilter question
> 
> > 
> > Hi,
> > 
> > I am trying to filter an svn dump to get only one module 
> (ModuleA)  from
> > the repository. A simplistic representation of the  repository is as
> > follows  -
> > 
> > trunk ---
> >    --- ModuleA
> >    --- ModuleB
> >    --- ModuleC
> >    --- ModuleD
> > 
> > tags ----
> >     --- ModuleATag1.1
> >     --- ModuleATag1.2
> >     --- ModuleATag2.0
> >     ...............
> >     --- ModuleBTagx.x
> >    ...........
> > 
> > I'm interested in getting /trunk/ModuleA  and all  
> > /tags/ModuleATagx.x
> > The svndumpfilter works fine for the trunk folder using the
> > svndumpfilter include command. However,  for the tags it runs into a
> > problem. The issue is that  the repo has been tagged by copying at 
> > the root level. So /tags/ModuleATagx.x have been created by 
> > copying /trunk.
> > Therefore /tags/ModuleATagx.x  have the following structure 
> > 
> > /tags/ModuleATagx.x -----
> >     ----ModuleA
> >     ----ModuleB
> >     ----ModuleC
> >     ......
> > 
> > Implying all tags contain the entire folder structure. 
> > 
> > My question is as follows - Is there anyway that I can 
> > filter the dump so as to get only
> > /tags/ModuleATagx.x/ModuleA?
> > 
> > Since the tags were created by copying at the root level,  
> > if I specify the /tags/ModuleATagx.x/ModuleA to be included
> > in the svnfilter dump command,  I do not get anything. If I
> > try to get the complete tag i.e.
> > /tags/ModuleATagx.x, I get an error since it needs the 
> > entire trunk.  I tried using svndumpfilter2 and svndumpfilter3,
> > to get the complete tags i.e. /tags/ModuleATagx.x, but did not
> > get much joy. They run too slowly and hang in the initial stages. 
> > 
> > This is a big repository with quite a few moves, so the above
> > is not the only issue that I am facing. However, I am able to
> > get around the other issues by some workarounds - like including
> > some extra folders or by splitting the dump into revisions and
> > hand selecting the ones to load. 
> > 
> > Regards
> > 
> 
A time consuming but possible work-around is to run dumpfilter
(repeatedly), EXcluding unwanted paths on each pass...

http://svnbook.red-bean.com/nightly/en/svn.ref.svndumpfilter.commands.c.
exclude.html

~ mark c