cwRsync got killed...

Benjamin R. Haskell rsync at benizi.com
Fri Nov 25 12:29:56 MST 2011


On Fri, 25 Nov 2011, Joachim Otahal (privat) wrote:

> Last cwrsync was 4.1.0, current is 4.2.0.
>
> It was avail on sourceforge.
>
> Itefix.no decided "we want money for coding and support" - that itself 
> is not wrong. Though _I_ never needed any rsync help on neither linux 
> and windows (including mixed) scenarios.
> But they killed their sourceforge downloads, all, including past 
> versions of cwrsync, including source.

That seems pretty antisocial of them.

They have a "Download source" link for 4.2.0 on their site ( 
http://www.itefix.no/i2/node/10650 ), still, which points to:

http://sereds.git.sourceforge.net/git/gitweb.cgi?p=sereds/sereds;a=tree

... though I'm not sure it's what it says it is.


They also don't seem to understand the implications of licensing 
something under the GPL.  (That page claims cwRsync is GPL-licensed.) 
They can't prevent the source code from being distributed, if that's the 
case.  So, the worst case without legal action is that one person buys a 
copy of cwRsync, then publishes the source code (which is permissible 
according to the GPL):

http://www.gnu.org/licenses/quick-guide-gplv3.html

In a better case, if anyone has the source code already, feel free to 
publish it.  That's how the GPL works.  So does BSD-licensing, actually. 
If you have the source code, you're free to redistribute it (with the 
restriction that the redistribution retains the same licensing terms and 
copyright information).


> The 4.2.0 client is still available on www.chip.de, but the server has 
> no alternative DL. We still have the filesize and the MD5 sum of 
> sourceforge.
>
> I'd vote for updating the download page http://rsync.samba.org/download.html.
>
> Apart from that: Anybody got lucky on cwRsyncServer_4.2.0_Installer.zip 
> 3961867 bytes MD5 c787dfa854775793d1a1b5c3502b57b5 ?

Sorry, no luck.  I also tried to see whether it still appeared under any 
outdated Sourceforge mirrors, but no dice.

-- 
Best,
Ben


More information about the rsync mailing list