Why does hg svn rebuildmeta prefer default-push to default when both exist? It seems more natural that default should be preferred (since it is used for pulling), at least from the point of my current workflow, which is as follows: I have a local hg clone of a remote svn repo which is set up as "default" and from which I'm pulling changes. I have also set up a BitBucket mirror to which I'm pushing changes (set up as "default-push" in the local clone). hg svn rebuildmeta (without using an explicit URI) fails because it tries to use default-push (which is a hg repository).
The "fix" for this, i.e. making hgsubversion prefer default, would be trivial but it might break some other workflows (clone a remote svn repo once, everyone else clones this repo but pushes back to the svn one).
Perhaps the right thing to do would be to use the path that starts with "svn+" (and continue preferring default-push if both do and it is preferred for some reason). I could write a patch if this is deemed acceptable.