Issue 207 - mtn revert inconsistent with/without inodeprints (monotone)
| Newsgroups | gmane.comp.version-control.monotone.devel |
|---|---|
| Message-ID | <2dbd085ef27fae135005fb52ec108d38@localhost> |
Hello, A new issue has been created and assigned to you: 207 - mtn revert inconsistent with/without inodeprints Project: monotone Status: New Reported by: Stephen Leake Labels: Type:Incorrect Behavior Priority:Medium Description: Steps to reproduce the problem: ------------------------------- 1. enable inodeprints via 'mtn refresh_inodeprints' 2. delete several files from disk via rm 3. 'mtn revert' one of the files Expected result: ---------------- file reverted Actual results: --------------- fatal warning about missing files. Without inodeprints, the revert succeeds. In the source, the problem is that 'work.cc maybe_update_inodeprints' calls update_current_roster_from_filesystem, which prints the warning. We need to disable warnings on some calls to update_current_roster_from_filesystem, or not call update-inodeprints for revert, or something. Output of `mtn version --full`: ------------------------------- -- Issue: https://code.monotone.ca/p/monotone/issues/207/