diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-03-12 22:53:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-03-12 22:53:43 -0400 |
| commit | b27760aa68d8c4cf1a1b0be3c3a5582539f857b5 (patch) | |
| tree | 872c0e9c2848fc6268b99b9c1d24d2599792092d /doc/forum.mdwn | |
| parent | 6a95240dff4799669ebc14e610f2555c32a86ef3 (diff) | |
Work around a bug in rsync (IMHO) introduced by openSUSE's SIP patch.
openSUSE patches rsync with a patch adding SIP protocol support.
https://gist.github.com/2026167
With this patch, running rsync with no hostname parameter is apparently
supposed to list SIP hosts on the network. Practically, it does nothing
and exits 0.
git-annex uses rsync in a very special way to allow git-annex-shell to be
run on the remote host, and so did not need to specify a hostname, or a
file to transfer as a rsync parameter. So it sent ":", a degenerate case of
"host:file".
But the patch cannot differentiate ":" with no host parameter
(a bug in the SIP patch surely).
Results were that getting files failed, as rsync seemed to succeed, but the
requested file failed to arrive. Also I think that sending files will
make git-annex think a file has been transferred to the remote when
really rsync does nothing.
The workaround for this buggy rsync patch is to use "dummy:" as the
hostname.
Diffstat (limited to 'doc/forum.mdwn')
0 files changed, 0 insertions, 0 deletions