Re: librsync 4GB bug

G'day Dave,

Note we are using the sourceforge lists/trackers/CVS etc. I'd suggest
subscribing to at least librsync-devel if you are doing devel work.
Cc'ing this to the devel list...

On Tue, 2006-02-21 at 21:51 +1100, dave kempe wrote:
> Hi Donovan,
> we have a guy working for the dole over here (under the community code 
> project - http://www.communitycode.org (site might be down atm).
> Anyway, he has being trying to slowly fix the librsync files over 4GB 
> bug which you can replicate using the simple tests like from this email:
> 
> http://lists.gnu.org/archive/html/rdiff-backup-users/2006-02/msg00015.html

Excellent!!! 

> Anyway, he seems to be finished - I think he used some MD4 bits from the 
> openssl libraries, and I have told him to post them to librsync-devel.
> I hope you haven't gone off and solved it all already, and of course I 
> would appreciate a once over of his code if you have time.
> It might be few days before its ready for a diff/patch submission yet.
> Its seems to work....

Get him to post the patch up on SF. I can also add him as a developer
and give him CVS access if he wants, but it's probably a good idea to
post this stuff initially as a patch so we can go over it before
committing it.

I did have plans to switch to using libmd, openssl, or our own md4sum