I too can confirm both the issue and the workaround on a freshly
installed and updated Ubuntu 10.04 LTS 64bit Rackspace Cloud Server
(used as a client, running rsync 3.0.7) connecting to a Debian server
which is running rsync 2.6.9
Please let me know if I can help in any way, as this bug was reall
I'm using rsync 3.0.7 and I still see this problem so it's not fixed in
3.0.7. Your workaround "--protocol=29" DOES work with rssh. I can help
provide more information about this observation.
** Changed in: rsync (Ubuntu)
Status: New => Confirmed
--
You received this bug notification be
