Rob Kramer wrote:
> Hi,
>
> I've converted my cvs repository to a svn dumpfile using cvs2svn. All
seems to
> work fine, but when I try to load it to a svn repository I get a failure:
>
> rob@lila:~/subversion/tools/cvs2svn> svnadmin create rob
> rob@lila:~/subversion/tools/cvs2svn> svnadmin load rob < cvs2svn-dump
...
> <<< Started new txn, based on original revision 59
> * deleting path : branches/mnapi-1-20-ils/mn/src/mnassert.c ...svn:
> Filesystem has no item
> svn: file not found: transaction `1n', path
> `branches/mnapi-1-20-ils/mn/src/mnassert.c'
>
> I'm using head btw. I'm not sure what's supposed to happen here, but I
noticed
> there has been a 'delete path' for mnassert.c already in revision 38..
>
> Dump was created using 'cvs2svn.py --dump-only
/home/rob/home/local/cvsroot'.
>
> Any idea?
As you have found out, cvs2svn has a few bugs still. Could you try copying
mnassert.c,v to an empty directory, and running cvs2svn on it, to see if
that still reproduces the bug?
If it does, and your repository does not contain private data, you could
file an issue in IssueZilla, and attach (compressed) mnassert.c,v to assist
in tracking down the bug.
If the repository does contain private data, you could remove it whilst
still preserving the revision structure, by deleting all contents between
the pairs of '@' characters following "text" and "log" for each revision.
This censored RCS file would probably also reproduce the bug.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 2 15:26:23 2003