[Bug 4375] New: Graft does not update largefiles correctly

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Fri Sep 19 13:54:33 CDT 2014


http://bz.selenic.com/show_bug.cgi?id=4375

          Priority: normal
            Bug ID: 4375
                CC: mercurial-devel at selenic.com, natosha at gmail.com
          Assignee: bugzilla at selenic.com
           Summary: Graft does not update largefiles correctly
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: andyt at playstudios.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: 3.1.1
         Component: largefiles
           Product: Mercurial

Graft does not work correctly with largefiles. It leaves the file unchanged
while the metadata for it points to a new file.

Steps to Reproduce:
On System A (this is a mac system)
1) Create a brand new repository
2) Check in a png file as large files
3) Commit and serve the repository

On System B (This is a windows system
1) Clone this repository
2) Create a new branch (TestBranch)
3) Add some text file in and add some commits

On System A
1) Make some changes to the png file
2) Commit it as update 1
3) Make some more changes to the png file
4) Commit it as update 2

On System B
1) Pull down the changes
2) Graft Update 1 to TestBranch

Results:
After a successful graft I expect png file to be in Update 1 state. Instead the
png file is in pre-Update 1 state and Mercurial reports uncommitted changes to
the png file.

Update --clean and revert does not refresh this file to Update 1 state. I
checked the checksum of the png file in .hg/largefiles and it is in the
original state. 

The only methods to recover this is to
1) Blow out the largefiles from .hg/largefiles and centralized cache, then do
an update --clean or
2) hg update -r null, answer use (c)hanged version, and then do hg update
--clean

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


More information about the Mercurial-devel mailing list