Changes:
Improve handling of incorrect permissions on backup repository during
restore operation. Closes Ubuntu bug #329722. (Andrew Ferguson)
Don't crash on zlib errors. Closes Debian bug #518531. (Andrew Ferguson)
Make sticky bit warnings quieter while determining file system abilities.
Closes Savannah bug #25788. (Andrew Ferguson)
Fix situation where destination file cannot be opened because of an access
error. Thanks to Dean Cording for the bug report. (Andrew Ferguson)
Fix --compare-hash options on Windows. Thanks to Serge Zub for the fix.
Don't crash when filesystem can't set ACL.
Properly disable hardlinks by default on Windows.
Fix Python 2.2 compatibility. Closes Savannah bug #25529.
Fix typo which caused failure when checking if another rdiff-backup
process is running on Windows.
New in v1.2.6 (2009/01/27)
---------------------------
Improve support for handling too long filenames under Windows. Too long
directory names and paths are still a problem. (Andrew Ferguson)
Print more helpful error messages when the remote command cannot be started
on Windows. Thanks to Dominic for the bug report. (Andrew Ferguson)
Fix --test-server option when used with remote Windows clients. Thanks to
Thanos Diacakis for testing. (Andrew Ferguson)
Fix --override-chars-to-quote option. (Andrew Ferguson)
New in v1.2.5 (2009/01/06)
---------------------------
Fix typo in robust.py which broke error reporting. Closes Savannah bug #25255.
Ignore Windows errors caused by too long filenames; the files are not yet
backed-up, but the backup process is no longer halted. (Andrew Ferguson)
New in v1.2.4 (2009/01/01)
---------------------------
Disable escaping trailing spaces and periods for now since it broke remote
restores. Thanks to Dominic for reporting the issue. (Andrew Ferguson)
New in v1.2.3 (2008/12/28)
---------------------------
The official Windows build now includes the librsync patch for files > 4GB.
This requires the Visual C++ 2008 redistributable, available from Microsoft.
The epoch is now a valid date. Closes Savannah bug #24814. (Andrew Ferguson)
Report that connection has dropped if filesystem operation returns ENOTCONN.
Closes Ubuntu bug #219920. (Andrew Ferguson)
Print a more helpful error message if we get an error while reading an old
current_mirror marker. This can happen because it has been locked or deleted
by a just-finished rdiff-backup process. Closes Ubuntu bugs #88140 and
#284506. (Andrew Ferguson)
Do not backup reparse points on native Windows. Thanks to John Covici for
reporting the issue. (Andrew Ferguson)
Support comments in rdiff-backup's ACL files and quote the quoting character
properly if user changed it. (Patch from Oliver Mulatz)
Print a more helpful error message if we cannot read the backup destination.
Closes Ubuntu bug #292586 (again). (Andrew Ferguson)
Print a more helpful error message if we cannot write to the backup
destination. (Andrew Ferguson)
Add ETIMEDOUT to the list of recoverable errors; when irrecoverable, a
ConnectionError is raised. Closes Ubuntu bug #304659. (Andrew Ferguson)
Suppress warnings about the deprecated sha module in Python 2.6. We'll remove
this after rdiff-backup is ported to Python 3. (Patch from Josh Nisly)
Test for symlink permissions now produces a functioning symlink. Thanks to
Julien Poffet for reporting the issue. (Andrew Ferguson)
Fix for crash when deleting read-only files on Windows. (Patch from Josh Nisly)
Fix for Python 2.2 in win_acls.py (Closes Savannah bug #24922).
Throttle verbosity of listattr() warning messages from 3 to 4. (Andrew Ferguson)
Escape trailing spaces and periods on systems which require it, such as
Windows and modern Linux with FAT32. (Andrew Ferguson)
Print nicer error messages in rdiff-backup-statistics (without tracebacks).
Closes Ubuntu bug #292586. (Andrew Ferguson)
Properly handle EINVAL "Invalid argument" errors when setting extended
attributes. Thanks to Kevin Fenzi for reporting the issue. (Andrew Ferguson)
Add warning message if pyxattr is below version 0.2.2. (Andrew Ferguson)
Add "Stale NFS file handle" (ESTALE) to the list of recoverable errors. Thanks
to Guillaume Vachon for reporting the issue. (Andrew Ferguson)
Workaround for broken support for symlink extended attributes in pyxattr <
0.2.2. Thanks to Leo Bergolth for reporting the issue. (Andrew Ferguson)
Handle ELOOP ("Too many levels of symbolic links") error when reading extended
attributes from symlinks. Closes Savannah bug #24790. (Andrew Ferguson)
Inform the user of which file has failed if an exception occurs during a
rename operation. (Andrew Ferguson)
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
Patch provided by Peter Schuller in PR 35419.
New in v1.0.5 (2006/11/11)
--------------------------
Fix a traceback due to an off-by-1 error in "--remove-older-than nB".
Fix a security violation when restoring from a remote repository.
(Patch from Charles Duffy.)
--list-at-time, --list-increments, and --list-increment-sizes should
now work from a read-only repository. (Bug reported by Wolfgang
Dautermann.)
patch provided by Daniel Neri in PR 32777
New in v1.0.4 (2006/01/15)
--------------------------
Files with ACLs will not be unnecessarily marked as changed (bug
report by Carsten Lorenz).
Another fix for long-filenames crash, this time when a long-named
directory with files in it gets deleted
Selection fix: empty directories could sometimes be improperly
excluded if certain include expressions involving a non-trailing '**'
were used. Bug reported by Toni Price.
Bug #15436 reported by Remy Blank: rdiff-backup would sometimes crash
on ACLs if the owning uname did not exist on destination.
New in v1.0.3 (2005/11/25)
--------------------------
Applied Alec Berryman's patch to update the no-compression regexp.
Alec Berryman's fs_abilities patch is supposed to help with AFS.
Fixed (version of) filename-too-long crash when quoting.
Due to very detailed error report from Yoav, fixed a "Directory not
empty" error that can arise on emulated filesystems like NFS and
EncFS.
Cleaned up remove older than report, and also stopped it from deleting
current data files if you specify a time later than the current
mirror.
--compare fix, now you don't need to specify the exact time of a
session to avoid a "no metadata" error.
New in v1.0.2 (2005/10/24)
--------------------------
Fix for spurious security violation from --create-full-path (reported
by Mike Bydalek).
Fix for bug 14545 which was introduced in version 1.0.1: Quoting
caused a spurious security violation. (Important for Mac OS X)
An error reading carbonfile data on Mac OS X should no longer cause a
crash. (Thanks to Kevin Horton for testing.)
Carbonfile support now defaults to off, even if the system appears to
support it. It can be manually enabled with the --carbonfile switch.
If you know something about Mac OS X and want to look at the
carbonfile code so it can be re-enabled by default, please do so :)
(help available from list)
Fix for bug #14799 reported by Bob McKay: Crash when backing up files
with high permissions (like suid) to some FAT systems.
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Lots of changes/bugfixes including:
rdiff-backup now writes its PID to current_mirror marker
Security fixes with --restrict-read-only, --restrict-update-only and
--restrict
OSX fixes
For a full list of changes see:
http://www.nongnu.org/rdiff-backup/CHANGELOG-stable
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
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.
