[Monotone-devel] Updated Issue 59 - mtn-0.32 fails incorrectly in mtn-0.33 multi-parented workspace (monotone)

[code]

Hello,

The following issue has been updated:

59 - mtn-0.32 fails incorrectly in mtn-0.33 multi-parented workspace
Project: monotone
Status: WontFix
Reported by: Thomas Keller
URL: https://code.monotone.ca/p/monotone/issues/59/
Labels:
 Component:Command Line UI
 Type:Incorrect Behavior
 Priority:Medium

Comments (last first):

# By Thomas Keller, Jan 14, 2011:

Out of scope

 Status: WontFix
 Owner: ---

# By Thomas Keller, Mar  3, 2007:

(This entry was imported from the savannah tracker, original location: 
https://savannah.nongnu.org/bugs/index.php?19188)

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.)

monotone version:
-----------------
mtn-0.32, mtn-0.33



--
Issue: https://code.monotone.ca/p/monotone/issues/59/