It seems you have a case of Divergent Bookmarks !
I believe that although I have not yet tried to recreate this on a remote repo to verify) that the remote repo believes that it has an update to the bookmark, which also updated the local repo. The name does not appear, although this is strange; is it called with spaces that the CLI cannot display, or maybe the "@" character itself? Perhaps you have a damaged entry in the bookmark file of the remote repo.
When you pull out a bookmark and the local and remote modules have updated the same bookmark, this creates a diverging bookmark. The remote version is added using "@ [path]", where the path is pulled from the [paths] section of the hgrc file based on the source of the remote repo. (For more information, see hg paths
.) The version "@ [path]" exists only locally until you merge and delete the diverging bookmark.
I think that if you merged and clicked on a remote repo, you would solve the bookmark problem and everything would be all right.
In your comment, you said that you intentionally use a bookmark with the name β@β referring to bookmark help: βIf you set a bookmark with the nameβ @ β, new repository clones will have this revision (and the bookmark is active) by default.
In this case, to prevent @default
from being created, you need the two conventions to be consistent with what set of changes @
should have; basically you need to correct the discrepancy. Given that you do not want to merge and return to the remote repo, this means updating the @
bookmark to match the remote repo.
Using the console example in your question, I believe that removing the diverging bookmark and resetting the @
bookmark according to the remote repo will not allow the discrepancy to continue:
hg book -d @default hg book @ -r 9 -f
source share