> http://nautilus.homeip.net/~lele/projects/cvsync >I would be more interested in packaging such a tool than a cvs2darcs, >one-way tool at the moment, since I have a lot of use for a two-way >sync. I'm hoping to investigate this other tool when it comes back >online.
tailor.py (in cvssync) has problems, too. It does not seem to handle conflicts between the "upstream" CVS and the darcs repository and it spits out a nice Python trace: myriam:tmp/from-tailor/foobar % (cd .. && tailor.py -v .) Updating 'foobar' from revision '2004-12-21 11:00:09 by bortzmeyer' Applying 1 upstream changesets Changeset 2004-12-21 11:03:10 by bortzmeyer: No longer interfaces in CVS Traceback (most recent call last): File "/usr/local/bin/tailor.py", line 33, in ? main() File "/home/bortzmeyer/tmp/tailor/vcpx/tailor.py", line 510, in main options.concatenate_logs) File "/home/bortzmeyer/tmp/tailor/vcpx/tailor.py", line 342, in update delayed_commit=single_commit) File "/home/bortzmeyer/tmp/tailor/vcpx/dualwd.py", line 55, in applyUpstreamChangesets delayed_commit=delayed_commit) File "/home/bortzmeyer/tmp/tailor/vcpx/source.py", line 77, in applyUpstreamChangesets res = self._applyChangeset(root, c, logger=logger) File "/home/bortzmeyer/tmp/tailor/vcpx/cvsps.py", line 268, in _applyChangeset raise ChangesetApplicationFailure( vcpx.source.ChangesetApplicationFailure: 'cvs update' returned status 256