-NEWS for rsync 2.6.7 (UNRELEASED)
+NEWS for rsync 2.6.7 (11 Mar 2006)
+
Protocol: 29 (unchanged)
Changes since 2.6.6:
longer complains about being unable to open the missing dir.
- Fixed a bug where the --copy-links option would not affect implied
- directories (see --relative) without --copy-unsafe-links.
+ directories without --copy-unsafe-links (see --relative).
- Got rid of the need for --force to be used in some circumstances with
--delete-after (making it consistent with --delete-before/-during).
- Rsync now ignores the SIGXFSZ signal, just in case your OS sends this
when a file is too large (rsync handles the write error).
+ - Fixed a bug in the Proxy-Authorization header's base64-encoded value: it
+ was not properly padded with trailing '=' chars. This only affects a
+ user that need to use a password-authenticated proxy for an outgoing
+ daemon-rsync connection.
+
+ - If we're transferring an empty directory to a new name, rsync no longer
+ forces S_IWUSR if it wasn't already set, nor does it accidentally leave
+ it set.
+
- Fixed a bug in the debug output (-vvvvv) that could mention the wrong
checksum for the current file offset.
+ - Rsync no longer allows a single directory to be copied over a non-
+ directory destination arg.
+
ENHANCEMENTS:
- Added the --append option that makes rsync append data onto files that
clump up all the removals at the end).
- A daemon now supersedes its minimal SIGCHLD handler with the standard
- PID-remembering version after forking to handle the request. This
- ensures that the generator can get the child-exit status from the
- receiver.
+ PID-remembering version after forking. This ensures that the generator
+ can get the child-exit status from the receiver.
- Use of the --bwlimit option no longer interferes with the remote rsync
sending error messages about invalid/refused options.