verify command does not verify contents of files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In response to a user question I ended up testing the 'verify' command to confirm it compared the contents of files, and it did not. Test methology (approximately reproduced from memory; don't cut'n'paste an run without reading; touching is to avoid duplicity triggering on mtime differences):
cd $somewhere
mkdir src
mkdir src-mtime
touch -r src src-mtime
echo test > src/test.txt
source src/test-mtime
touch -r src/test.txt src/test-mtime
duplicity src file://./dest
mv dest dest2 # easy way to peneatrate archive cache
echo TEST > src/test.txt # same length, different contents
touch -r src/test-mtime src/test.txt
touch -r src-mtime src
duplicity verify file://./dest2 src
The verify should now succeed in spite of the fact that the contents of the test.txt file differs.
Related branches
- duplicity-team: Pending requested
-
Diff: 202 lines (+90/-94)1 file modifiedtesting/functional/test_verify.py (+90/-94)
Changed in duplicity: | |
status: | New → Fix Released |
Changed in duplicity: | |
milestone: | none → 0.7.01 |
importance: | Undecided → Medium |
This feature is now available using --compare-data.
A test that tweaked mtimes and atimes after editing, similar to the above (coincidentally), was included in the linked branch, now merged into trunk. See testing/ functional/ test_verify. py test_verify_ compare_ data_changed_ source_ file_adjust_ mtime