largefile: use `set_possibly_dirty` instead of `normallookup`
authorPierre-Yves David <pierre-yves.david@octobus.net>
Sun, 18 Jul 2021 23:43:08 +0200
changeset 47721 d46d3aefd00b
parent 47720 b0314d8deee1
child 47722 47dce5a99eab
largefile: use `set_possibly_dirty` instead of `normallookup` Differential Revision: https://phab.mercurial-scm.org/D11163
hgext/largefiles/overrides.py
--- a/hgext/largefiles/overrides.py	Sun Jul 18 23:42:22 2021 +0200
+++ b/hgext/largefiles/overrides.py	Sun Jul 18 23:43:08 2021 +0200
@@ -1785,7 +1785,9 @@
         # mark all clean largefiles as dirty, just in case the update gets
         # interrupted before largefiles and lfdirstate are synchronized
         for lfile in oldclean:
-            lfdirstate.normallookup(lfile)
+            entry = lfdirstate._map.get(lfile)
+            assert not (entry.merged_removed or entry.from_p2_removed)
+            lfdirstate.set_possibly_dirty(lfile)
         lfdirstate.write()
 
         oldstandins = lfutil.getstandinsstate(repo)