Re: Problem with vendor branches
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
COMPAN Arnaud wrote: >> De : Michael Haggerty [mailto:[email protected]] >> >> COMPAN Arnaud wrote: >>> I'm using cvs2svn (v2.3.0) to migrate our CVS repository to SVN. >>> I'm having a problem in the handling of vendor branches by cvs2svn. >>> [...] It seems that on CVS, we have >>> the 1.1.1.1 revision on the trunk but the 1.1.1.2 revision on SVN. >> What makes you think that there is a problem? The output that you >> quoted looks exactly as I would expect. >> >> The way that cvs2svn works, there could be differences in how CVS tags >> (like $Revision$ or $Id$) are expanded, but otherwise the contents of >> the file on SVN trunk *should* be identical to those in a non-tag CVS >> checkout, namely those from your CVS 1.1.1.2 revision. >> > > 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 ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2403016 To unsubscribe from this discussion, e-mail: [[email protected]].