In my experience this is often the result of a head in the past that you
are not looking at because you are focused on your local tip. You can
pull this head from a co-worker (they may have created it with a -f) and
then not notice it for one reason or another.
I expect hg heads will be your friend here and then merge with whatever
head that is. Or if it is an error, close it.
Tom
On 4/29/2025 9:06 AM, Uwe Brauer via Mercurial wrote:
Hi
I tried to push and received
hg push helix
pushing to
https://UweBrauer@helixteamhub.cloud/uam/projects/HG-Bioquim/repositories/mercurial/HG-Bioquim
searching for changes
abort: push creates new remote head 0d30bfb88252 on branch 'year-2024-25'
(merge or see 'hg help push' for details about pushing new heads)
So far so good, I pulled and merged the head, my graph looks now like
◉ changeset: 1297:989993c13c46
│╲ tag: tip
│ │ Branch: year-2024-25
│ │ Author: Uwe Brauer <o...@mat.ucm.es>
│ │ Date: Tue, 29 Apr 2025 14:48:42 +0200
│ │ Phase: secret
│ │ Parent: 1209:273b05441da7
│ │ Parent: 1296:0d30bfb88252
│ │ Summary: Merge tip with revision 1209, which was a topological head
│ │
As one could see the heads 0d30bfb88252 and 273b05441da7 are merged,
However when I try to push I receive the same message, I checked there
are now other topological heads. So I am puzzled now.
Hg push -f
could be a solution, but this is one of last resorts
Any ideas?
_______________________________________________
Mercurial mailing list
Mercurial@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial
