You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Reilly, Michael" <mr...@techtarget.com> on 2006/02/09 15:22:10 UTC

svndumpfilter --drop-empty-revs errors

Hello, I'm new to the list.  I am a release engineer at a media company
in Massachusetts.  We're moving to Subversion, from both CVS and older,
ill-configured Subversion setups.

 

We're running SVN 1.2.3 on RHEL 3.2.3 with Apache 2.0.46.

 

I am trying to split one large repository, with a number of projects in
it, into smaller repositories.  I dumped the entire large repository
(/repos/pd) to pd.dump, filtered it to only include the top level
directory "PDS", dropping and renumbering revisions, and outputting to
pds.dump.  When I load the pds.dump into a new repository, I get an
error "No such revision: 812".

 

I've googled and looked through the archives of the SVN Dev and SVN
Users lists.  The only reference I've found deals with a bug associated
with Node-copyfrom-rev nodes.  Yes, most of my errors do have
Node-copyfrom-rev fields.  However, the first error is a text version
change, not copyfrom.

 

The commands were:

$ svnadmin dump /repos/pd > pd.dump

$ svndumpfilter include PDS --drop-empty-revs --renumber-revs < pd.dump
> pds.dump

# no errors

$ svnadmin load /repos/pds.temp < pds.dump

# non Node-copyfrom-rev error on rev 812 and possibly others

# Node-copyfrom-rev errors on revs 882, 892, 1346, 2579, 3212, 3326,
3473

 

The node info for revision 812 is below.  I've excluded the data.

Revision-number: 812   

Prop-content-length: 165

Content-length: 165    

                       

K 7                    

svn:log

V 61

don't use FindBin module on NFS mount for performance reasons

K 10

svn:author

V 9

ahartford

K 8

svn:date

V 27

2005-03-01T23:43:54.664325Z

PROPS-END

 

Node-path: PDS/IO_Manager/trunk/perl/lib/perl/PDS/Log.pm

Text-content-md5: ea7e14859f33a47c18d6e4ef0628da99

Node-action: change

Node-kind: file

Text-content-length: 1947

Content-length: 1947

 

There are only two other references in the entire original repository to
this file, both are within the tree.  The size of filtered dumpfile is
3994 versions.

 

When I run svndumpfilter without "--drop-empty-revs --renumber-revs",
the load succeeds.  But, of course, I want to move the tree without the
empty revisions.

 

Has anyone come across this issue before?  Does anyone have any ideas
about a resolution?  Thank you for any comments or help.

  -Michael

 

-- 

Michael P. Reilly  mreilly@techtarget.com  781-657-1766

TechTarget  Release engineer,  Product development

117 Kendrick St, Suite 800, Needham, MA 02494

 

There's so many different worlds, So many different suns.
And we have just one world, But we live in different ones.

 


Re: svndumpfilter --drop-empty-revs errors

Posted by Blair Zajac <bl...@orcaware.com>.
On Feb 9, 2006, at 7:22 AM, Reilly, Michael wrote:

> Hello, I’m new to the list.  I am a release engineer at a media  
> company in Massachusetts.  We’re moving to Subversion, from both  
> CVS and older, ill-configured Subversion setups.
>
> We’re running SVN 1.2.3 on RHEL 3.2.3 with Apache 2.0.46.
>
> I am trying to split one large repository, with a number of  
> projects in it, into smaller repositories.  I dumped the entire  
> large repository (/repos/pd) to pd.dump, filtered it to only  
> include the top level directory “PDS”, dropping and renumbering  
> revisions, and outputting to pds.dump.  When I load the pds.dump  
> into a new repository, I get an error “No such revision: 812”.
>
> I’ve googled and looked through the archives of the SVN Dev and SVN  
> Users lists.  The only reference I’ve found deals with a bug  
> associated with Node-copyfrom-rev nodes.  Yes, most of my errors do  
> have Node-copyfrom-rev fields.  However, the first error is a text  
> version change, not copyfrom.
>
>
IIRC correctly, I'm on a plane now, there's a bug that is fixed in  
the latest 1.3.0 svnadmindump filter that fixes the revision counting.

I would get 1.3.0 and see if that fixes your problem.  You can dump  
the existing 1.2.3 repository with 1.3.0 tools with no problems.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/



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