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

Re: cvs2svn moved to its own project

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2004-02-25 09:53:07 CET

C. Michael Pilato wrote:

> The knowledge could be useful, yes. The Subversion book documents the
> major issues that caused us grief.

I went through that process last week, since I decided to separate our
one big repsitory into lots of tiny repositories.

> What it does *not* document are
> certain outright bugs in svndumpfilter that we weren't aware of until
> today, and which I'm working to fix right now.

Like getting copyfrom revision numbers off by one for example? I used
--drop-empty-revisions and --renumber-revisions and ended up with
results like:
Revision-number: 10
Node-path: tags/Project_1_05
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 10
Node-copyfrom-path: trunk/Project
which is obviously wrong.

Second problem:
We initially had a layout like:
which proved to be not-so-good :-)

So in the early days of our repository I created the structure:

for each project and moved the content of trunk/ProjectA to ProjectA/trunk

After filtering out all the revisions that contained trunk/ProjectA and
ProjectA/trunk, I ended with a complete revision history for ProjectA,
but svnadmin was not able to import the dump file. Errors like
non-existing paths were thrown at me. I had to manually edit the
node-path for each revision before the restructuring took place. Maybe I
used the wrong hammer, but these were my two major headaches.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 25 09:52:50 2004

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.