+NEWS for rsync 2.6.6 (28 Jul 2005)
+Protocol: 29 (unchanged)
+Changes since 2.6.5:
+
+ SECURITY FIXES:
+
+ - The zlib code was upgraded to version 1.2.3 in order to make it more
+ secure. While the widely-publicized security problem in zlib 1.2.2 did
+ not affect rsync, another security problem surfaced that affects rsync's
+ zlib 1.1.4.
+
+ BUG FIXES:
+
+ - The setting of flist->high in clean_flist() was wrong for an empty list.
+ This could cause flist_find() to crash in certain rare circumstances
+ (e.g. if just the right directory setup was around when --fuzzy was
+ combined with --link-dest).
+
+ - The outputting of hard-linked files when verbosity was > 1 was not right:
+ (1) Without -i it would output the name of each hard-linked file as
+ though it had been changed; it now outputs a "is hard linked" message for
+ the file. (2) With -i it would output all dots for the unchanged
+ attributes of a hard-link; it now changes those dots to spaces, as is
+ done for other totally unchanged items.
+
+ - When backing up a changed symlink or device, get rid of any old backup
+ item so that we don't get an "already exists" error.
+
+ - A couple places that were comparing a local and a remote modification-
+ time were not honoring the --modify-window option.
+
+ - Fixed a bug where the 'p' (permissions) itemized-changes flag might get
+ set too often (if some non-significant mode bits differed).
+
+ - Fixed a really old, minor bug that could cause rsync to warn about being
+ unable to mkdir() a path that ends in "/." because it just created the
+ directory (required --relative, --no-implied-dirs, a source path that
+ ended in either a trailing slash or a trailing "/.", and a non-existing
+ destination dir to tickle the bug in a recent version).
+
+ ENHANCEMENTS:
+
+ - Made the "max verbosity" setting in the rsyncd.conf file settable on a
+ per-module basis (which now matches the documentation).
+
+ - The support/rrsync script has been upgraded to verify the args of options
+ that take args (instead of rejecting any such options). The script was
+ also changed to try to be more secure and to fix a problem in the parsing
+ of a pull operation that has multiple sources.
+
+ - Improved the documentation that explains the difference between a
+ normal daemon transfer and a daemon-over remote-shell transfer.
+
+ - Some of the diffs supplied in the patches dir were fixed and/or
+ improved.
+
+ BUILD CHANGES:
+
+ - Made configure define NOBODY_USER (currently hard-wired to "nobody") and
+ NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we
+ find in the /etc/group file).
+
+ - Added a test to the test suite, itemized.test, that tests the output of
+ -i (log-format w/%i) and some double-verbose messages.
+
+\f
NEWS for rsync 2.6.5 (1 Jun 2005)
Protocol: 29 (unchanged)
Changes since 2.6.4:
- An OS that has a binary mode for its files (such as cygwin) needed
setmode(fd, O_BINARY) called on the temp-file we opened with
- mkstemp(). (Fix derived from the cygwin's 2.6.3 rsync package.)
+ mkstemp(). (Fix derived from cygwin's 2.6.3 rsync package.)
- Fixed a potential hang when verbosity is high, the client side is
the sender, and the file-list is large.
(since the forked process already has a copy of the exclude list,
there's no need to send them a set of duplicates).
- - When --progress is specified, the output of items that the generator
- is creating (e.g. dirs, symlinks) is now integrated into the progress
- output without overlapping it. (Requires protocol 29.)
+ - The output of the items that are being updated by the generator (dirs,
+ symlinks, devices) is now intermingled in the proper order with the
+ output from the items that the receiver is updating (regular files)
+ when pulling. This misordering was particularly bad when --progress
+ was specified. (Requires protocol 29.)
- When --timeout is specified, lulls that occur in the transfer while
the generator is doing work that does not generate socket traffic
- We now reset the "new data has been sent" flag at the start of
each file we send. This makes sure that an interrupted transfer
with the --partial option set doesn't keep a shorter temp file
- than the current basis file when no new data has been transfered
+ than the current basis file when no new data has been transferred
over the wire for that file.
- Fixed a byte-order problem in --batch-mode on big-endian machines.
\f
Partial Protocol History
RELEASE DATE VER. DATE OF COMMIT* PROTOCOL
+ ?? ??? 2006 2.6.7 29
+ 28 Jul 2005 2.6.6 29
01 Jun 2005 2.6.5 29
30 Mar 2005 2.6.4 17 Jan 2005 29
30 Sep 2004 2.6.3 28
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff