monotone - Bugs: bug #19188, mtn-0.32 fails incorrectly in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #19188: mtn-0.32 fails incorrectly in mtn-0.33 multi-parented workspace
Submitter: | Thomas Keller <tommyd> | ||
Submitted: | Sat 03 Mar 2007 07:54:24 AM UTC | ||
Category: | command line UI | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: | mtn-0.32, mtn-0.33 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-02a9.
Corresponding source code
If one calls any workspace-related command (e.g. mtn status) with mtn-0.32 in a 0.33 workspace which has more than one parent, monotone fails with an invariant error
I(rev.edges.size() == 1)
in work.cc, line 96, method get_work_rev() (in 0.32)
Now, since 0.32 is no longer fixable, but should already contain workspace version checking code, I guess this kind of bug is probably still be present in maybe another way in the current head?
Is ensured for version 0.x, that a workspace format change in 0.x+1 will error out in 0.x properly with "workspace too new, upgrade your mtn install", to a certan degree, of course? (Not assuming that the actual workspace version checking code will change.)