I'm running tailor on a cron job at night to mirror changes from a cvs
repository into a svn repository. Most often it goes without a hitch,
but it seems a problem is creeping in with certain modules. Here's the
whole scenario:
I'm running tailor 0.9.20. When I run tailor like so,
tailor -v --config-file dev.cfg dev
with the config file
[DEFAULT]
use-propset = True
encoding = utf8
root-directory = /subversion/.sync/hybrid
subdir = dev
[dev]
target = svn:dev
start-revision = INITIAL
source = cvs:dev
[reverse_dev]
source = svn:dev
target = cvs:dev
[cvs:dev]
module = dev
repository
= :pserver:[EMAIL PROTECTED]:/streamsage/cvsroot
[svn:dev]
module = dev
repository = file:///subversion/research
I get the following output:
00:01:43 [I] Updating "dev" in "/subversion/.sync/hybrid"
00:01:43 [I] $ svn ls file:///subversion/research
00:01:43 [I] [Ok]
00:01:43 [I] Applying pending upstream changesets
00:01:43 [I] Changeset "2001-06-18 06:01:26 by stage"
00:01:43 [I] Log message: Removed this file, as everything is
now consolidated into product/Merm/XXXServer/config/config.xml
-- lewis
00:01:43 [I] /subversion/.sync/hybrid/dev $ cvs
-d :pserver:[EMAIL PROTECTED]:/streamsage/cvsroot
-q update -d -r 1.12 research/config.xml
00:01:44 [I] [Ok]
00:01:44 [I] /subversion/.sync/hybrid/dev $ svn add --quiet
--no-auto-props --non-recursive research/config.xml
00:01:44 [W] [Status 1]
00:01:44 [I] /subversion/.sync/hybrid/dev $ svn commit
--file /tmp/tailordMgIA5svn research/config.xml
00:01:44 [W] [Status 1]
00:01:44 [C] Couldn't reply changeset
00:01:44 [C] Upstream change application failed
Failure applying upstream changes: /subversion/.sync/hybrid/dev
$ svn commit --file /tmp/tailordMgIA5svn research/config.xml
returned status 1 saying
svn: Commit failed (details follow):
svn: '/subversion/.sync/hybrid/dev/research/config.xml' is not
under version control
The strange thing is that there should be no file
dev/research/config.xml. If I type cvs co dev, there's no such file in
the research subdirectory. This is always the case: changes are being
committed to a file which is not under version control in either CVS or
Subversion. Could this be a file which someone added to and then removed
from CVS between invocations of my cron job? Are commits being performed
in the wrong order? Could this be the result of trying to infer what
should have been atomic commits in CVS, could CVS do such a thing?
I'm just speculating here. Any help will be appreciated.
David Houghton
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
