monotone-devel
[Top][All Lists]
Advanced

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

Re: [Monotone-devel] Bugreport update ID ("database schema has changed"


From: Christof Petig
Subject: Re: [Monotone-devel] Bugreport update ID ("database schema has changed" <- I doubt that)
Date: Fri, 10 Dec 2004 09:34:08 +0100
User-agent: Mozilla/5.0 (X11; U; Linux ppc; de-AT; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5

Nathaniel Smith schrieb:
On Fri, Dec 10, 2004 at 08:28:24AM +0100, Christof Petig wrote:
$ cat MT/revision
ba3f2f3c077ad8413c7f6fca4f4dab048812b325

$ monotone update 6a5a7ef7e6d53e2f22918f099ec03963f1cbb090


(Why are you doing this? :-))

It looked more elegant than 'echo 6a5a >/MT/revision ; monotone revert' :-S

monotone: selected update target 6a5a7ef7e6d53e2f22918f099ec03963f1cbb090
monotone: moving ROADMAP -> MT/tmp/1
monotone: moving figures/branch-heads.pdf -> MT/tmp/3
monotone: moving figures/branch-heads.png -> MT/tmp/4
...
monotone: updating work.hh to 7b232a0b0730bdedf75afbddaec8b0c60034a9f7
monotone: updated to base revision 6a5a7ef7e6d53e2f22918f099ec03963f1cbb090

$ ...
$ monotone diff
monotone: misuse: file disappeared but exists in manifest: figures/branch-heads.pdf


Hmm, having stared at the graph some, my tentative guess is that it's
calculating the changeset via a path that goes through some of the
corrupt changesets that happened at around the .changesets ->
.monotone propagation.  Since the "corruption" is that those
changesets have spurious adds, and we're passing through them
backwards, it would make sense that you're seeing spurious deletes?

If this diagnosis is right, you're just hitting a _former_ bug, and
there's not a lot to do except wait until we figure out how to clean
those things up...

Hm. IIRC I did cross that propagate. Sigh. Resolving to echo/revert :-(

    Christof

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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