[Bug] [cvs2svn] Invalid assumption can lead to 1.1.1.1 revisions being silently dropped.

cvs2svn say:
# The first revision on a vendor branch is always the same as
# the revision from which the branch sprouts, e.g., 1.1.1.1 is
# always the same as 1.1, so there's no need to further modify
# 1.1.1.1 from however it is in the copy from 1.1.

This is false. Example:

1) Add+commit a file normally
2) Import a file of the same name
There is no guarantee that these were identical

Or, more rigourously:

mkdir testroot
cd testroot
export CVSROOT=`pwd`/testrepo
cvs init
cvs co -d testwc -l .
cd testwc
mkdir foo
cvs add foo
cd foo
echo "Hello" > foo
cvs add foo
cvs ci -m.
mkdir tmp
cd tmp
echo "Goodbye" > foo
cvs import -m. foo VENDOR IMPORT1
cd ..
cvs co -p -r 1.1 foo/foo
cvs co -p -r 1.1.1.1 foo/foo
cd ../..
cvs2svn --dump-only testrepo
fgrep Goodbye cvs2svn-dump
# Look! Contents of rev 1.1.1.1 are not in dumpfile!

I will IssueZilla this, with a summary of any discussion that occurs, in a
few days time.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 13 17:15:02 2003