monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Cvssync problems


From: Brian Downing
Subject: [Monotone-devel] Cvssync problems
Date: Tue, 27 Sep 2005 14:34:33 -0500
User-agent: Mutt/1.2.5i

I've been playing with this a little bit.  Remote CVS version is
1.11.20.  (Note that I have verify_depth set to 0 in this build, but I
checked that the problems happen in the same place with the default.)

One problem:

:; monotone-cvssync -d ~/somat.db -b com.somat.cvs.test cvs_pull 
:ext:address@hidden:/cvs Test
enter passphrase for key ID address@hidden:
monotone: bytes in | bytes out
monotone:       24 |         1
monotone: verifying new revisions (this may take a while)
monotone: file ids | revisions
monotone:       24 |         5
monotone: fatal: std::logic_error: cvs_sync.cc:847: invariant 
'I(!e->xfiles.empty())' violated
monotone:
monotone:
monotone: this is almost certainly a bug in monotone.
monotone: please send this error message, the output of 'monotone 
--full-version',
monotone: and a description of what you were doing to address@hidden
monotone: wrote debugging log to 
/home/bdowning/projects/somat/edaq-boot/MT/debug

Debug log attached as debug1.gz, and I can provide a tarball of the CVS
module on request.

Second, in a larger repository that I made some test changes to:

:; monotone-cvssync cvs_push
enter passphrase for key ID address@hidden:
monotone: bytes in | bytes out
monotone:      550 |       852 |        0
monotone: warning: unhandled server response "F"
monotone: wrote debugging log to 
/home/bdowning/projects/somat/edaq-boot/MT/debug

Debug log attached as debug2.gz.

:; monotone-cvssync --full-version
monotone 0.22 (base revision: 8d9f57c3dc0deac34ed36cac1fd2e34d5a29056d)
Running on: Linux 2.6.12.timerhack #1 Mon Sep 12 18:35:38 CDT 2005 i686
Changes since base revision:
new_manifest [ae40786f35d118d064db208603e21cb4f9cdfe90]

old_revision [8d9f57c3dc0deac34ed36cac1fd2e34d5a29056d]
old_manifest [ae40786f35d118d064db208603e21cb4f9cdfe90]

Again, the verify_depth is 0 but that doesn't affect these errors.

-bcd




reply via email to

[Prev in Thread] Current Thread [Next in Thread]