Package: rdiff-backup
Version: 1.1.5-4
Severity: important
It seems to me that rdiff-backup is innovative and
useful.
I used it to back up a remote computer onto a
local one, and eventually the remote computer's
hard drive failed.
When I checked the backup copy, I was surprised to
learn that rdiff-backup had silently changed uids
and gids. Furthermore, unless it's smart enough to
check that the new uids or gids aren't already in
use, it seems to me that the data corruption is
irreversible.
One might say that using
--preserve-numerical-ids
avoids the problem, but that's little consolation
to someone who reasonably assumed their data
wouldn't be altered, and who's faced with the
somber reality of having no backup.
I suggest that rdiff-backup *not* alter data by
default. That way, nothing would be irreversibly
lost.
Thanks,
Kingsley
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages rdiff-backup depends on:
ii libc6 2.3.6-7 GNU C Library: Shared libraries
ii librsync1 0.9.7-1 Library which implements the rsync
ii python 2.4.4-1 An interactive high-level object-o
ii python-support 0.5.6 automated rebuilding support for p
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.2.2-1 module for manipulating POSIX.1e A
ii python-pyxattr 0.2.1-1.1 module for manipulating filesystem
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
