RE: Problem with vendor branches
COMPAN Arnaud <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
> COMPAN Arnaud wrote: > > > > In fact, the file from the CVS checkout is different than from the > SVN checkout. > > On the CVS checkout (the head), the file is the same as the 1.1.1.1 > revision of the vendor branch. > > On the SVN checkout (the trunk), the file is the same as the 1.1.1.2 > revision of the vendor branch. > > According to the documentation, cvs2svn behaves correctly but at the > end, contents are different. > > Is it normal ? > > I overlooked in your original email that the file doesn't appear to > have > an active vendor branch. If that is true, there is indeed a problem. > I > still would wager that there is some kind of screwy corruption in your > repository, but it could also be a cvs2svn bug. Please send a complete > bug report (see FAQ) so that we can investigate. > > Michael I think I found the problem. After the first 'cvs import', we used the 'cvs admin -b' command to change the default branch. In that case, the behavior of cvs2svn (updates trunk to reflect changes on a non-trunk default branch) is not the good one because the default branch has changed. I send you a bug report. Regards, Arnaud ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2403543 To unsubscribe from this discussion, e-mail: [[email protected]].