Hi, while looking through the old open bug reports on rsync I came across this one...
On Sun 19 May 2002, Jon Middleton wrote: > Package: rsync > Version: 2.5.5-0.1 > Severity: normal > > When using the following command line > > /usr/bin/rsync --partial -Rl > ftp.uk.debian.org::debian/dists/stable/main/binary-i386/Release > /var/cache/debian-proxy > > it exits with the following error message > > rsync: recv_generator: mkdir "dists/stable/main": No such file or > directory (2) stat dists/stable/main : No such file or directory > > And it has only created a dangling symlink in the traget directory > (dists/), it looks like it's failing to create the target directory > along with the symlink. The current version is subtlely different: rsync: recv_generator: mkdir "/var/cache/debian-proxy/dists/stable/main" failed: No such file or directory (2) rsync: stat "/var/cache/debian-proxy/dists/stable/main" failed: No such file or directory (2) rsync: recv_generator: mkdir "/var/cache/debian-proxy/dists/stable/main/binary-i386" failed: No such file or directory (2) rsync: stat "/var/cache/debian-proxy/dists/stable/main/binary-i386" failed: No such file or directory (2) rsync: mkstemp "/var/cache/debian-proxy/dists/stable/main/binary-i386/.Release.SwToaR" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1166) The problem is that ftp.uk.debian.org::debian/dists/stable is not a directory, but a symlink to woody (at this time). The -l option tells it to create symlinks as symlinks, hence it creates /var/cache/debian-proxy/dists/stable as a symlink to "woody". That directory does not exist, so it fails to complete. A workaround is to create /var/cache/debian-proxy/dists/woody/ by hand, or to explicitly rsync woody and not stable. Adding the -d option might help, however in this particular instance it won't as ftp.uk.debian.org doesn't have a version of rsync that supports it. Basically rsync will only automatically create one level of directory on the receiving end unless -r (recursive) has been specified. Perhaps the error message might be a bit clearer, especially in this instance, but I doubt that it's a real bug; it's the documented way rsync should work in this case. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
