> Craig Barratt wrote:
> | I'm surprised rsync would change in a manner that would not be
> | backward compatible. I follow the rsync mail list, but maybe
> | not closely enough.
> I am too!
> | Does this bug happen with CVS rsync talking to CVS rsync? If so, that's
> | something we should take up on the rsync mail list. Perhaps I need to
> | delve into the CVS code a little to understand what has changed.
> Yes, it happens with CVS->CVS, as well as release->CVS I believe too.
This issue should now be resolved. File::RsyncP passes the exclude
arguments to the server/sender via ARGV, rather than via the socket
interface. ARGV support for server/sender exclude arguments was
removed in rsync CVS, since it wasn't a supported feature. But the
rsync developers recently re-added support at our request. 2.6.3pre1
does not include the fix, but the next release should have excludes
that work correctly. See:
I'm also updating File::RsyncP to implement excludes in the correct
way, via the socket interface, rather than exploiting a non-supported
feature in rsync.