Lapo Luchini <[email protected]> writes:
> Stephen Leake wrote:
>> Hugo Cornelis <[email protected]> writes:
>>
>>> I have a weird problem with monotone. It is reporting two heads, but
>>> inspecting the log reveals that there is only one head:
>>
>> This is fixed in 0.48; upgrade to that, then run 'db regenerate_caches'.
>
> Uh?
> Doesn't "mtn log --last 5" show the current workspace release and some
> of his ancestors?
> And thus, have no reason at all to show the "sister" head release?
> (which would imply descending the tree, not only going up)
>
> I don't understand what "bug" was fixed in 0.48 regarding this. ^_^
There was a bug in the branch heads cache. There is no bug report for
it, but it's in NEWS:
- In 0.46 and 0.47, monotone could sometimes get confused
about which revisions were the heads of a particular branch.
This would happen when a new branch cert was added to a
revision that was an ancestor of one or more of the current
heads of the branch, most commonly during netsync when
multiple people had performed identical merges. This is
fixed now. 'db check' will identify the problem; if your
database currently gives incorrect 'heads' results, or 'mtn
bug' on 'merge', you can fix it by running 'mtn db
regenerate_caches'.
--
-- Stephe
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
