[librsync-devel] Re: state of the rsync nation?
(revisited 6/2003 from 11/2000)
abo at minkirri.apana.org.au
Mon Aug 4 13:02:45 EST 2003
On Mon, 2003-08-04 at 11:05, Martin Langhoff wrote:
> Donovan Baarda wrote:
> > For the record, librsync version 0.9.6 is _almost_ ready in CVS. A bug
> >has been detected but not isolated yet for large files (2G+). If it's
> >not squashed soon I'm tempted to release anyway with a KNOWN_BUGS that
> >reports this.
Last night I found and squashed a bug that caused the problem. I'm
waiting on feedback from the user that reported it to confirm it is now
> I am just looking around for hints on compiling librsync under cygwin
> (gcc), and happened to find this post of your promising 0.9.6, which
> runs under cygwin...
I know that post was ages ago, but due to work commitments I never got a
chance to release it. Every time I got a small chance to look at it
again, I kept finding little niggly things that really should have been
fixed before release.
The CVS is only intermittently updated, so I only bother tagging on
release, which still hasn't happened yet. The CVS HEAD is the current
release candidate. I don't commit unless it passes a "make distcheck" so
it should never be broken.
> Are the sources at least tagged, so I can get the mfrom CVS? What tags?
Your timing is impeccable. Just last night I finalised the MSVC updates
and fixed the last known bug. That means there is nothing outstanding
for the release... this should be 0.9.6, but I'm giving it a day or so
to get feedback before I tag and release.
There is a delay on SF between developer and anon CVS, so it is possible
the final checkins are not yet visible. In the meantime, there is a
tarball available at;
This compiles and builds on win32 using cygwin and/or MSVC.
Donovan Baarda <abo at minkirri.apana.org.au>
More information about the rsync