Re: svndumpfilter --drop-empty-revs errors

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
<blair@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