verify command does not verify contents of files

Bug #601785 reported by Peter Schuller on 2010-07-05
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Duplicity
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

Changed in duplicity:
status: New → Fix Released

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

Changed in duplicity:
milestone: none → 0.7.01
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers