I tried to push a local repo to my user repo, this is what I did: $ hg clone -r FIREFOX_47_0_1_RELEASE_RUNTIME https://hg.mozilla.org/build/tools $ ssh hg.mozilla.org clone tools-47 (Proceed? yes, Create an empty repository? yes, Proceed? yes) $ hg -R tools push ssh://hg.mozilla.org/users/raliiev_mozilla.com/tools-47 pushing to ssh://hg.mozilla.org/users/raliiev_mozilla.com/tools-47 searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 6865 changesets with 14643 changes to 1993 files remote: *** pushing unrelated repository *** remote: remote: Changeset 663964646638 introduces a new root changeset into this repository. This remote: almost certainly means you accidentally force pushed to the wrong remote: repository and/or URL. remote: remote: Your push is being rejected because this is almost certainly not what you remote: intended. remote: transaction abort! remote: rollback completed remote: pretxnchangegroup.single_root hook failed abort: push failed on remote

The build/tools repo has multiple root changesets (4 to be precise). There is a global hook on hg.mozilla.org that prevents pushing new roots to all repos. It is arguably a bug that this enforces its will on user repos too. A workaround is to create a server-side clone of the build/tools repo using `ssh hg.mozilla.org clone tools-47` (as opposed to an empty repo). Since you won't do an initial push, no new roots will be introduced.

Wontfix then? I can live with that work around.

Yeah, WONTFIX (but only for lack of desire to fix the underlying issue).