Re: [Monotone-devel] What the status of 0.26?

[Petr Ovtchenkov]

On Thursday 09 March 2006 15:08, Nathaniel Smith wrote:
> On Thu, Mar 09, 2006 at 09:44:50AM +0300, Petr Ovtchenkov wrote:
> > May be I miss something, but can you clarify the status of 0.26 and
> > procedure of pull from venge.net?
> >
> > [the reason of question is a problems with pull with 0.26pre1 client,
> > inspired by two heads in net.venge.monotone branch].
> 
> I think you may be looking for the information here?
>   http://article.gmane.org/gmane.comp.version-control.monotone.devel/6128
> 
> I don't know of any reason multiple heads would be a problem; there is
> a problem pulling the net.venge.monotone.contrib.webhost branch with
> 0.26pre1, because it uses the recently merged root rename features.
> The solution is to pull net.venge.monotone alone, and build it.  (I
> should probably do an 0.26pre3 release soon, for this and other
> reasons...)
> 
> Does that answer your question?

Mmmm, I think that problem present not only in 
net.venge.monotone.contrib.webhost:

> monotone --db=venge.mtn pull venge.net "net.venge.monotone*" --exclude 
> net.venge.monotone.contrib.webhost
monotone: doing anonymous pull; use -kKEYNAME if you need authentication
monotone: connecting to venge.net
monotone: first time connecting to server venge.net
monotone: I'll assume it's really them, but you might want to double-check
monotone: their key's fingerprint: 70a0f283898a18815a83df37c902e5f1492e9aa2
monotone: warning: saving public key for address@hidden to database
monotone: finding items to synchronize:
monotone: bytes in | bytes out | certs in | revs in
monotone:   11.6 k |     0.7 k |        0 |       0
monotone: bytes in | bytes out |    certs in |   revs in
monotone:   23.1 M |     0.7 k |  5532/20162 | 1369/5012
monotone: fatal: std::logic_error: roster.cc:1362: invariant 
'I(right_uncommon_ancestors.find(right_marking.birth_revision) != 
right_uncommon_ancestors.end())' 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: discarding debug log (maybe you want --debug or --dump?)
301.842u 27.301s 8:46.21 62.5%  0+0k 0+0io 11pf+0w


> monotone --db=venge.mtn heads -b net.venge.monotone
monotone: branch 'net.venge.monotone' is currently unmerged:
b291a1bf3545129d8a5ac7c5e0f73db31b139f4c address@hidden 2005-02-23T09:24:48
b9ffc0175872ac09df9e2fdfc39fede32441e77b address@hidden 2005-03-15T06:40:53
e4aa815f818090a978ede00ba8e9819b2f18b53c address@hidden 2005-02-25T07:58:44


(client is 0.26pre1, with you netsync-fixup.patch).

  - Petr Ovtchenkov