Hello,
The following issue has been updated:
207 - mtn revert inconsistent with/without inodeprints
Project: monotone
Status: Fixed
Reported by: Stephen Leake
URL: https://code.monotone.ca/p/monotone/issues/207/
Labels:
Type:Incorrect Behavior
Priority:Medium
Comments (last first):
# By Stephen Leake, Jun 23, 2012:
fixed in nvm, 327090160ca10bd6df9e9132c3e39cea5abc88fe
Status: Fixed
# By Stephen Leake, Jun 22, 2012:
The current test 'restricted_commit_with_inodeprints' reports a similar problem with missing files.
It also suggests a solution; only update the inodeprints on a restricted set of files. That would fix the revert issue as well.
Owner: stephe
# By Stephen Leake, Apr 10, 2012:
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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.