Data corruption local rep, bitbucket repo has more heads than local one?

Uwe Brauer oub at mat.ucm.es
Thu May 25 08:47:51 UTC 2017




    > Notice that all of these revisions are branch heads. If you type 'hg
    > heads -t' I suspect you'll see only one head. See 'hg help heads' for
    > why.

Nope, I see them all

    > Notice that this is a superset of what you had before.


    > What does 'hg verify' say? I think you've just got some divergent
nothing really interesting
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
165 files, 81 changesets, 288 total revisions


    > history, and you might want to merge them together. That is, nothing
    > is corrupted, you've just got 3 different copies of the same revision,
    > probably with different contents (921b9b8667b1, fc056d395e04, and
    > 77560cdc346d). You can either use the web interface on bitbucket to
    > strip them, or you can just pull and merge the spurious heads back
    > together with 'hg merge'.

Right, I am however puzzled that my original repo does not show the
heads. Maybe I just delete the bitbucket repo re create it and push from
my local one. I am afraid that collaborators might run into problems
when they try to pull.

    > Does 'hg outgoing' say anything is outgoing to the server? I
    > suspect it'll say everything is pushed. :)

yes

    > _______________________________________________
    > Mercurial mailing list
    > Mercurial at mercurial-scm.org
    > https://www.mercurial-scm.org/mailman/listinfo/mercurial




More information about the Mercurial mailing list