[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svndumpfilter --drop-empty-revs errors

From: Blair Zajac <blair_at_orcaware.com>
Date: 2006-02-12 00:04:25 CET

On Feb 9, 2006, at 7:22 AM, Reilly, Michael wrote:

> Hello, Im new to the list. I am a release engineer at a media
> company in Massachusetts. Were moving to Subversion, from both
> CVS and older, ill-configured Subversion setups.
> Were 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.
> Ive googled and looked through the archives of the SVN Dev and SVN
> Users lists. The only reference Ive 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.


Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
Subversion training, consulting and support
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 12 03:44:45 2006

This is an archived mail posted to the Subversion Users mailing list.