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

svndumpfilter oddities

From: Chris Morgan <chmorgan_at_gmail.com>
Date: 2005-09-28 16:42:08 CEST

Using svn 1.2.0 (I didn't see any changes in the changelog that would
prompt me to move to 1.2.3 and try again, but I can do so)

I dumped a repo with:

svnadmin dump /somerepo > repo.dump

cat repo.dump | svndumpfilter --drop-empty-revs --renumber-revs
/some/path > partial.dump

When I try to load this back I get errors like:

------- Committed revision 135 >>>

<<< Started new transaction, based on original revision 136
svnadmin: No such revision 136

If I edit the dump file and go to 'Revision-number: 136' I noticed
that inside of this revision there was a 'Node-copyfrom-rev: 136'.
This seemed odd that rev 136 would refer to itself and after looking
at other examples I changed it to 'Node-copyfrom-rev: 135' and
everything seems happy.

I had a couple of questions. First was whether this minor change was
correct. I didn't want to be modifying these files by hand and end up
screwing up the history for the import.

I was also wondering whether this is a new issue with svndumpfilter.
It seems like when renumbering things svndumpfilter shouldn't make a
revision that refers to either itself or a future transaction, only
historical ones.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 28 16:48:04 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.