<div class="gmail_quote">On Sat, Apr 24, 2010 at 9:04 AM, Enrico Gallo <span dir="ltr"><<a href="mailto:enrico.gallo@gmail.com">enrico.gallo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
the fist one is already described in<br>
<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536078" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536078</a> , but I don't<br>
find any reply<br></blockquote><div><br></div><div>I don't recall seeing that one in the main rsync bugtracking, but I may have just forgotten it. That is still a bug in the current code.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
the second one, when parsing log file, absolute paths of deleted files show pwd instead of destination directory<br></blockquote><div><br></div><div>You didn't provide your copy command, but at least you mentioned that one side was 2.6.9, which makes me believe that this is the bug affecting you (fixed in 3.0.0):</div>
<div><br></div><div><div>- Fixed a bug in the %f logfile escape when receiving files: the destination path is now included in the output (e.g. you can now tell when a user specifies a subdir inside a module).</div></div></div>
<div><br></div>You can avoid that by using %n or upgrading rsync.<div><br>..wayne..<br>
</div>