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

Re: cvs2svn urgently needs a verification tool

From: <kfogel_at_collab.net>
Date: 2004-02-15 01:33:10 CET

Tobias Ringstrm <tobias@ringstrom.mine.nu> writes:
> We (i.e. the Subversion project) urgently need a tool that can at
> verify that the data is correct in trunk and all the tags and branches
> after a conversion. It could e.g. run cvs export and svn export and
> compare the data for all tags, etc.
>
> Automatic log message checking for each file should also be possible,
> but it's not as important, and it's also much harder.
>
> Such a tool would be great for running tests during development, but
> also to provide more confidence to users that the data is correct
> after a conversion. It's nothing short of a disaster if the tagged
> code (or whatever you put in you repositories) is incorrent after a
> conversion.

Totally agree that we need such a tool.
 
> Unfortunately cvs2svn does have such bugs now. :-(

Do you know of one? We need it filed if so :-).

The only open correctness issue related to branches is issue #1510,
which is about trunk checkouts behaving the same from both CVS and
SVN, not about the branches or tags themselves being wrong.

> Maybe we should
> make cvs2svn print a banner saying that it should not be used until it
> has received more testing.

It should probably print a banner telling you *not* to delete your old
CVS repository.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 15 02:35:04 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.