Subject: Re: pkg/15501: rsync development branch causes corruption with alpha server
To: None <gendalia@iastate.edu>
From: Greg A. Woods <woods@weird.com>
List: netbsd-bugs
Date: 02/05/2002 19:10:50
[ On , February 5, 2002 at 21:24:26 (-0000), gendalia@iastate.edu wrote: ]
> Subject: pkg/15501: rsync development branch causes corruption with alpha server
>
> 2.5.x is the development branch of rsync. 2.4.8 is the patched stable
> branch version of rsync.
This is not correct.
From my examination of the rsync master CVS repository it would appear
to me that in fact 2.5.2 is the official current release and that the
2.4.x branch is merely a maintenance branch. Indeed there's even a
recent 2.3.3 release (i.e. more recent than 2.5.2) on BRANCH-2-3, the
maintenance branch for 2.3.x.
If you read the NEWS file for 2.4.8 and 2.3.3 you'll see that they
include only the security fixes, nothing more. From what I've heard
these releases would never have been made if there had been no
"security" issue in those branches.
You'll find in their repository that that BRANCH-2-4 was created after
release-2-5-1, and before BRANCH-2-3. These were apparently
after-thoughts, not indications of "stability". Indeed there are very
serious operational bugs remaining in 2.3.3 and 2.4.8.
In release terms 2.5.2 is already the second patch release for 2.5.x.
Each of those patch releases went through several beta pre-releases, as
evidenced by the "-pre*" tags in the repository.
I don't know about any file corruption issues with 2.5.2 (I've seen
none), but I do know that it is the first release, ever, that has
managed to run fully to completion in several example scenarios where
I've tried to use rsync. I.e. it does not suffer from any of the "hang"
bugs of earlier releases.
pkgsrc/net/rsync should most definitely be at 2.5.2, not anything
earlier, and indeed as of Jan 26 (rev 1.38 of Makefile), it is.
--
Greg A. Woods
+1 416 218-0098; <gwoods@acm.org>; <g.a.woods@ieee.org>; <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>