WORKAROUND remote repository changed while pushing - please try again
Since the move to Heptapod 0.12, people have been experiencing push problems with this obscure message.
Workaround
Install or upgrade hg-evolve to 9.3.x
Explanation
Heptapod 0.12 includes in particular #221 (closed), which prevents topic unaware clients to pull topical revisions and lots of subsequent trouble, be it for traditional Mercurial users or for down-to-earth CI systems.
The price to pay is that it requires a version bump in hg-evolve
(more specifically of the topic
extension), bringing in the ability for the client to tell the server that it is, in fact, topic aware.
We've also had at least one user report where the problem was that topic
was not activated on the client side. An assessment should be made for the exact condition.
Heptapod-side resolution
Upgrade hg-evolve to a version in which the corresponding bug (report) is solved.