Package: duplicity
Version: 0.6.18-3
Severity: normal
Tags: upstream
The "verify" command of duplicity does not check file contents, it only
compares modification time and size of files and directories.
For example, if one issues the following commands,
mkdir /tmp/src
echo hello > /tmp/src/a
touch -r /tmp/src/a /tmp/refdate
duplicity full --no-encryption /tmp/src file:///tmp/dst
echo world > /tmp/src/a
touch -r /tmp/refdate /tmp/src/a
duplicity verify --no-encryption file:///tmp/dst /tmp/src
then the last verify does not report any difference, although /tmp/src/a HAS
changed.
In other words, one cannot rely on duplicity to check that the data on disk
are identical to those backed up.
Best regards,
g
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii libc6 2.13-38
ii librsync1 0.9.7-9
ii python 2.7.3-4+deb7u1
ii python-gnupginterface 0.3.2-9.1
Versions of packages duplicity recommends:
pn python-paramiko <none>
ii rsync 3.0.9-4
Versions of packages duplicity suggests:
ii lftp 4.3.6-1+deb7u2
pn ncftp <none>
pn python-boto <none>
pn python-cloudfiles <none>
pn python-gdata <none>
pn python-pexpect <none>
pn tahoe-lafs <none>
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
