[Bug 6094] New: `hg incoming` incorrectly reports that csets that are obsolete but present both locally and remotely will be pulled in from remote

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=6094

            Bug ID: 6094
           Summary: `hg incoming` incorrectly reports that csets that are
                    obsolete but present both locally and remotely will be
                    pulled in from remote
           Product: Mercurial
           Version: 4.9
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: evolution
          Assignee: bugzilla at mercurial-scm.org
          Reporter: faheem at faheem.info
                CC: mercurial-devel at mercurial-scm.org,
                    pierre-yves.david at ens-lyon.org

I have a local repository, which I'm pushing to a remote non-publishing
repository.

I just noticed that a `hg incoming` gives a list of csets, even though local
and remote should be synced, and therefore `hg incoming` should be empty.

However, `hg incoming --hidden` is indeed empty.

The list of csets appears to be present but obsolete on both local and remote.
Some, but not all of them, are pruned csets. And this is a small subset of the
total number of obsolete csets present on local and remote.

I also see that the number of heads reported locally is 2, while the number of
heads reported remotely is 3. The difference is a cset that remote says is
obsolete, but `hg heads` still shows it, and it looks like this.

@  changeset:   1562:7b12947817ab

Shouldn't it have an x, since it's obsolete?

I did a local clone of the remote, and obsolete csets still show up in there.

More information available on request. But bear in mind this is a live
repository, so the bug symptoms might disappear at any moment.

https://bz.mercurial-scm.org/show_bug.cgi?id=4202 is a similar, related bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.