rsync - Mar 2005 - rsync error: protocol incompatibility (code 2) at main.c(451)

Wayne, others,

Using the same version on server and client, I still got this error. This 
was still based on last night's CVS (HEAD-20050314-1745GMT) and I am 
certain both side's versions are identical. :)

	...
	source/sudosh-1.4.7-1.rf.src.rpm
	       98373 100%  536.69kB/s    0:00:00  (798, 99.9% of 244497)
	Invalid packet at end of run [sender]
	rsync error: protocol incompatibility (code 2) at main.c(451)

The rsync run completed without errors apart from that message.

--   dag wieers,  dag@wieers.com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]

On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers
wrote:
> 	Invalid packet at end of run [sender]
It would help to know what options you had enabled.

..wayne..

On Mon, 14 Mar 2005, Wayne Davison wrote:
> On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote:
> > 	Invalid packet at end of run [sender]
> 
> It would help to know what options you had enabled.
Damn, I was planning to include those. Here they are:

	-avHl --progress --delete-after --delay-updates --exclude bert/ 
	--exclude dries/ --exclude redhat/6.2 --exclude redhat/8.0
	-e "/usr/bin/ssh -oCompression=no" 

Thanks,
--   dag wieers,  dag@wieers.com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]

On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers
wrote:
> 	Invalid packet at end of run [sender]
OK, this was a combination of --delay-updates and --hard-links that was
causing a problem at the end of the run.  I've checked in a fix to CVS,
and the latest "nightly" tar file has this fix present.  I'm
confident
that will take care of the problem for you.  Thanks for the help!

..wayne..