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

Re: cvs2svn: converted repository doesn't match cvs

From: Max Bowsher <maxb_at_ukf.net>
Date: 2003-09-18 20:08:06 CEST

Daniel Patterson wrote:
>> I've just completed a test conversion of a CVS repository,
>> around 800M of CVS data, 5700 (cvs2svn calculated) revisions.
>>
>> I've been doing some validation, initially just on the trunk,
>> to compare if what cvs2svn gives us is what we see in CVS.
>> Unfortunately, this is not the case.
>>
>> What I do to test:
>>
>> svn export http://server/repos/trunk
>> cvs export -rHEAD dealernet
>> diff -u -r dealernet trunk
>>
>> This gives me the attached diff. There seem to be a couple
>> of problems here:
>>
>> 1) A file that shouln't be on the trunk is (a quick look
>> at the RCS file shows two revisions, the second one
>> is dead, and no branches are involved).

cvs2svn unneccessarily and unwisely ignores deletions at r1.1.
Since your RCS file contains r1.0(Exp) and r1.1(dead), the deletion is
erroneously skipped.

This is clearly a bug in cvs2svn.

>> 2) Two files have had "@" characters appended to them.

This seems to be a bug in RCS. (cvs2svn does uses it to extract the revision
texts).

>> Do these strike anyone as existing bugs, or should I open
>> new ones?

Please file both, but indicate that the second one is actually a fault
in RCS.

>> I can provide the RCS files in question under verbal NDA.

Thankyou. I have trimmed them into minimal reproduction cases, with no
sensitive data. I will send them to you privately for you to approve the
censored versions. Please add them as attachments to the bug reports.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 21 14:39:08 2003

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.