When you push the successors of a formely bookmarked changeset, the bookmark is not properly updated remotely because the successors is not a descendants of the precursors. The bookmark code which decide to update bookmark should take obsolete relation into account.
Fixed by http://selenic.com/repo/hg/rev/a7b3fdaf768d Pierre-Yves David <pierre-yves.david@logilab.fr> bookmark: take successors into account when updating (issue3561) When we rewrite a bookmarked changeset, we want to update the bookmark on its successors. But the successors are not descendants of its precursor (by definition). This changeset alters the bookmarks logic to update bookmark location if the newer location is a successor of the old one[1]. note: valid destinations are in fact any kind of successors of any kind of descendants (recursively.) This changeset requires the enabling of the obsolete feature in some bookmark tests. (please test the fix)