Ok'ed wiz@/snj@/davids (at) idiom.com
From the CHANGELOG:
New in v0.12.7 (??????????)
---------------------------
Altered file selection when restoring so excluded files will not be
deleted from the target dir. The old behavior was technically
intended and documented but not very convenient. Thanks to Oliver
Kaltenecker for bug report.
Fixed error when --restrict path given with trailing backslash. Bug
report by Åke Brännström.
Backported regress fix from 0.13.x. Bug noticed by Alan Horn.
Added error-correcting fsync suggestion by Antoine Perdaens.
rdiff-backup may work better with NFS now.
Fix for regress warning code: rdiff-backup should warn you if you are
trying to back up a directory into itself.
Changes since 0.12.5:
* Yet another unreadable file non-root regress bug fix.
* Added --list-increment-sizes option from the development branch.
Previously this option was in the man page but was omitted in the code
(thanks to Michael Schwendt for report).
* Regressing and restoring should now take less memory when processing
large directories (noticed by Luke Mewburn and others).
* When regressing, remove mirror_metadata and similar increments first.
This will hopefully help regressing a backup that failed because disk
was full (reported by Erik Forsberg).
* Fixed rather important quoting problem: quoting directives like
--windows-mode were simply ignored when rdiff-backup was running
remotely! I'm surprised no one noticed this. Are none of you using
--windows-mode or similar?
* Fixed handling of (lack of) daylight savings time. Earlier bug would
cause some files to be marked an hour later. Thanks to Troels Arvin
and Farkas Levente for bug report.
New in v0.12.5 (2003/09/27)
---------------------------
Fixed bug in --test-server when using --restrict security options
(test would fail improperly). Thanks to Maik Schreiber for report.
--list-changed-since and --list-at-time now work remotely.
Thanks to Morten Werner Olsen for bug report.
Fixed logic bug that could make restoring extremely slow and waste
memory. Thanks for Jacques Botha for report.
Fixed bug restoring some directories when mirror_metadata file was
missing (as when made by 0.10.x version).
Regressing and restoring as non-root user now works on directories
that contain unreadable files and directories as long as they are
owned by that user. Bug report by Arkadiusz Miskiewicz. Hopefully
this is the last of the unreadable file bugs...
New in v0.12.4 (2003/09/13)
---------------------------
Specified socket type as SOCK_STREAM. (Error reported by Erik
Forsberg.)
Fixed bug backing up unreadable regular files and directories when
rdiff-backup is run by root on the source site and non-root on the
destination side. (Reported by Troels Arvin and Arkadiusz
Miskiewicz.)
If there is data missing from the destination dir (for instance if a
user mistakenly deletes it), only warn when restoring, instead of
exiting with error.
Fixed problems with --restrict options that would cause proper
sessions to fail. Thanks to Randall Nortman for error report.
File examples.html added to distribution; examples section removed
from man page.
- Over 1500 lines of changelog since 0.10.2
- Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a
compressed text file in the rdiff-backup-data directory
- No longer seems compelled to send symlinks every time
Provided in PR 18577 by David.S at idiom dot com, some modifications
by me to use buildlink2 files, and to specify the correct version of
python required.
Rdiff-backup backs up one directory to another, possibly over a network.
The target directory ends up a copy of the source directory, but extra
reverse diffs are stored in a special subdirectory of that target directory,
so you can still recover files lost some time ago. The idea is to combine
the best features of a mirror and an incremental backup. Rdiff-backup also
preserves subdirectories, hard links, dev files, permissions, uid/gid
ownership (if it is running as root), and modification times. Finally,
rdiff-backup can operate in a bandwidth efficient manner over a pipe, like
rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive
up to a remote location, and only the differences will be transmitted.
