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

            Bug ID: 6603
           Summary: Wrong modified file in hg status in share context
           Product: Mercurial
           Version: 5.7.1
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzi...@mercurial-scm.org
          Reporter: georges.raci...@octobus.net
                CC: mercurial-devel@mercurial-scm.org
    Python Version: ---

I have a case where a file is always displayed as modified in `hg status`, even
after `hg revert` or `hg update -C` or even after a sequence of updates.

The repository was cloned with the `share-pool` configuration item (the `share`
extension is active).

Recreating the share or recloning the actual repository in the pool resolves
the problem.

I tried both hg 5.7.1 on Python 3.8 and 5.9.2 on Python 3.9 (the latter with or
without Rust).

I have not been able in a limited time to find a small reproduction, so I made
a tarball with the full repo and an offending share (6MB). 

Here's how to download the tarball and reproduce the bug (more details in the
README file)

$ cd /tmp
/tmp $ curl -o status-bug.tgz
https://static.octobus.net/bug-reproductions/gracinet-status-bug-2021-10-15.tgz 
/tmp $ tar xzf status-bug.tgz 

(if one untars in some other directory, the status-bug/share/.hg/sharedpath
file will have to be adjusted accordingly).

/tmp $ cd status-bug
/tmp/status-bug $ ls
README share  share-pool
/tmp/status-bug $ cd share
/tmp/status-bug/share $ hg st
M heptapod-ci.yml
/tmp/status-bug/share $ hg rev heptapod-ci.yml 
/tmp/status-bug/share $ hg st
M heptapod-ci.yml
/tmp/status-bug/share $ hg update -C .
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
/tmp/status-bug/share $ hg st         
M heptapod-ci.yml
/tmp/status-bug/share $ hg debugdirstate | grep heptapod-ci
n 644       1787 unset               heptapod-ci.yml

(notice the 'unset' mtime)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to