This looks like this upstream bug, fixed in 1.7: http://mercurial.selenic.com/bts/issue2364 FWIW the fix (http://selenic.com/hg/rev/545ec1775021 - excluding the test update) applies cleanly on top of 1.6.4. Regards, Wagner