Several people have now all stumbled upon the following problem: Mercurial 1.7 was updated and it includes a change where the repositories it creates by default are not backward compatible with earlier versions. Now that 1.7.1 has been out for a bit people are updating to the latest command line version of Mercurial. Now normally it’s perfectly fine to have an older version of Mercurial in MacHg. Normally I upgrade the version in MacHg in a staggered fashion due to bug testing and stability. (Also since it’s a Front end to Mercurial it doesn’t matter if a new feature is added to Mercurial proper since if an interface isn’t coded into MacHg then the feature is not used.) For a couple of weeks now the version I have used internally in my development has been 1.7.1. Thus due to this problem with version mismatch I am issuing a pre release of version MacHg 0.9.10 for those people who need it:
I would do this as a full release but unfortunately I am not in my home city in front of my home computer, thus the keys I use for Sparkle are not present on my machine. As soon as I get in front of my home machine I will issue an update that goes through sparkle. For now though use the link above. (Incidentally there are several non-critical fixes in 0.9.10 which you can peruse on the official bit bucket site.)
(Note, just in case you were wondering, trying to use MacHg 0.9.9 on a repository created by Mercurial 1.7+ will not in any way damage the repository, but it won’t work. To make it work use MacHg 0.9.10 above…)
Update: I have now officially released MacHg 0.9.10. So the pre-release version has been removed and replaced by the official version.