similar to: Rsync 3.0.4 released

Rsync version 3.0.4pre2 is now available for release testing. This is a bug-fix release with the only "enhancement" being the adding of a way to interact with an overly-restrictive server that refuses rsync's behind-the-scenes use of the -e option. I hope this will be the final pre-release prior to 3.0.4, so please do test this and send email to the rsync mailing list with any

Rsync version 3.0.4pre2 is now available for release testing. This is a bug-fix release with the only "enhancement" being the adding of a way to interact with an overly-restrictive server that refuses rsync's behind-the-scenes use of the -e option. I hope this will be the final pre-release prior to 3.0.4, so please do test this and send email to the rsync mailing list with any

Rsync version 3.0.4pre1 is now available for release testing. This is a bug-fix release with the only enhancement being the adding of a way to interact with an overly-restrictive server that refuses rsync's behind-the-scenes use of the -e option. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the

Rsync version 3.0.4pre1 is now available for release testing. This is a bug-fix release with the only enhancement being the adding of a way to interact with an overly-restrictive server that refuses rsync's behind-the-scenes use of the -e option. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the

I think it's about time to start adding some new features to rsync 3 instead of just making bug fixes, so I'm planning to starting work on version 3.1.0. This will start the use of a new version numbering idiom where feature releases increment the sub-version number, while patch releases continue to increment the sub-sub-version number. I'm not using an odd/even scheme for

I have released rsync version 2.6.6. This release is a bug-fix release to handle a null-pointer bug that turned up in rsync's version of zlib 1.1.4 (this is not the recent zlib 1.2.2 security fix, which did not affect rsync) and to squash a few other minor bugs. To deal with the zlib issue, rsync has been upgraded to include zlib 1.2.3. Here is a list of the changes between 2.6.5 and 2.6.6:

I have released rsync version 2.6.6. This release is a bug-fix release to handle a null-pointer bug that turned up in rsync's version of zlib 1.1.4 (this is not the recent zlib 1.2.2 security fix, which did not affect rsync) and to squash a few other minor bugs. To deal with the zlib issue, rsync has been upgraded to include zlib 1.2.3. Here is a list of the changes between 2.6.5 and 2.6.6:

I've released version 2.6.0 of rsync. Two important things to note in the new release: 1. The default remote shell is now "ssh" unless you tell the configure you want to use something else. 2. Some bug fixes in the include/exclude code, while making things work properly, have resulted in some user-visible changes for certain wildcard strings. Read the

Rsync version 3.0.5pre1 is now available for release testing. This is a bug-fix release. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the changes since 3.0.4, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.5pre1-NEWS You can download the source tar file and its signature

Rsync version 3.0.5pre1 is now available for release testing. This is a bug-fix release. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the changes since 3.0.4, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.5pre1-NEWS You can download the source tar file and its signature

Rsync version 3.0.5pre2 is now available for release testing. This is a bug-fix release. I hope this is the final pre-release for 3.0.5, so please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. The changes since 3.0.5pre1: - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from file when the root of the transfer

Rsync version 3.0.5pre2 is now available for release testing. This is a bug-fix release. I hope this is the final pre-release for 3.0.5, so please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. The changes since 3.0.5pre1: - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from file when the root of the transfer

https://bugzilla.samba.org/show_bug.cgi?id=5795 Summary: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo:

I have released rsync 3.2.6. A fairly simple bugfix release. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.6 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.6.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.6.tar.gz.asc See the website for other downloads,

I have released rsync 3.2.6. A fairly simple bugfix release. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.6 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.6.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.6.tar.gz.asc See the website for other downloads,

Hi Wayne, I see that a couple of patches from the rsync-patches tar have disappeared, like acls.diff or xattrs.diff yet I don't see the changes in the code. Is there a reason for their removal? Were they applied differently on the code and are no longer needed? Thanks for any info on this. Regards, Michal Ruprich On 8/7/20 7:45 AM, Rupert Gallagher via rsync wrote: > Rsync 3.2.2

Rsync 3.2.2 ransfer rate on my pet hardware is really poor, so every improvement counts. I noted that rsync writes a gmon file on the source path and leaves it there when it terminates. When the source path is read-only, rsync complains that it cannot write in it. For optimal use of the input bus, no write commands should be used there. Can you look into it? Also, I have 12GB of cache in ecc ram

I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz.asc See the

I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here: https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz https://rsync.samba.org/ftp/rsync/rsync-3.2.3.tar.gz.asc See the

I have released rsync 3.0.3. This is a bug-fix release that contains no new features. To see a full summary of the changes since 3.0.2, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.3-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.3.tar.gz http://rsync.samba.org/ftp/rsync/src/rsync-3.0.3.tar.gz.asc