Hi, Some explanations regarding cwRsync:
cwRync installers (both client and server) are now available as a paid download bundle. Installer sources, however, are still available as free upon contact. Please keep in mind that installer sources are not enough to build cwRsync installers: You need to build up a complete Cygwin environment, compile/copy binaries in the package. It may be time consuming. That's why paying a reasonable price for the installer itself can be an alternative as well. NB! I have notified Rsync website before changes are made. Best regards Tev cwRsync maintainer/developer On Sat, Nov 26, 2011 at 8:00 PM, <rsync-requ...@lists.samba.org> wrote: > Send rsync mailing list submissions to > rsync@lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.samba.org/mailman/listinfo/rsync > or, via email, send a message with subject or body 'help' to > rsync-requ...@lists.samba.org > > You can reach the person managing the list at > rsync-ow...@lists.samba.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of rsync digest..." > > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > > --------------------------------------- > Today's Topics: > > 1. Re: cwRsync got killed... (Benjamin R. Haskell) > 2. Re: cwRsync got killed... (Steven Levine) > 3. [Bug 8416] Please include systemd service file > (samba-b...@samba.org) > > > ---------- Forwarded message ---------- > From: "Benjamin R. Haskell" <rs...@benizi.com> > To: "Joachim Otahal (privat)" <j...@gmx.net> > Date: Fri, 25 Nov 2011 14:29:56 -0500 (EST) > Subject: Re: cwRsync got killed... > 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 <http://www.itefix.no/i2/node/10650>), > still, which points to: > > http://sereds.git.sourceforge.**net/git/gitweb.cgi?p=sereds/** > sereds;a=tree<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<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 <http://rsync.samba.org/download.html>. >> >> Apart from that: Anybody got lucky on cwRsyncServer_4.2.0_Installer.**zip >> 3961867 bytes MD5 c787dfa854775793d1a1b5c3502b57**b5 ? >> > > Sorry, no luck. I also tried to see whether it still appeared under any > outdated Sourceforge mirrors, but no dice. > > -- > Best, > Ben > > > > ---------- Forwarded message ---------- > From: "Steven Levine" <stev...@earthlink.net> > To: rsync@lists.samba.org > Date: Fri, 25 Nov 2011 15:50:21 -0800 > Subject: Re: cwRsync got killed... > In <alpine.LNX.2.01.1111251354300.14380@hp.internal>, on 11/25/11 > at 02:29 PM, "Benjamin R. Haskell" <rs...@benizi.com> said: > > Hi, > > >> But they killed their sourceforge downloads, all, including past > >> versions of cwrsync, including source. > > >That seems pretty antisocial of them. > > Interesting. They are allowed to do what they want with the binaries, but > the sources are another issue. As I read the GPL, they must continue to > provide access to the sources for at least three years after the binary > was last distributed. > > In addition, they must provide access to the actual sources used to build > the binaries. For example, if itefix modified any of the rsync sources > used to build the binaries, it's not sufficient to provide a link to the > rsync sources at samba.org. > > >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. > > To me, it looks the what they say it is, which is the install component of > cwRsync. I don't know enough about Windows installers to say if it is > complete. > > >They can't prevent the source code from being distributed, if that's the > >case. > > Well, they are not really trying to do that. What they are doing is > removing access at a site they control for the sources corresponding to > binaries they distributed in the past. > > Perhaps, someone that is interested in cwRsync should contact itefix and > ask them if there are any source code modifications. > > Another option is to contact the FSF and ask them to review the issue. > This is after all, part of their charter. > > Regards, > > Steven > > -- > ---------------------------------------------------------------------- > "Steven Levine" <stev...@earthlink.net> eCS/Warp/DIY etc. > www.scoug.com www.ecomstation.com > ---------------------------------------------------------------------- > > > > > ---------- Forwarded message ---------- > From: samba-b...@samba.org > To: rsync...@samba.org > Date: Sat, 26 Nov 2011 04:23:35 +0000 > Subject: [Bug 8416] Please include systemd service file > https://bugzilla.samba.org/show_bug.cgi?id=8416 > > --- Comment #3 from Cristian RodrÃguez <crrodrig...@opensuse.org> > 2011-11-26 04:23:34 UTC --- > There is a quirk to be aware of in this systemd unit. > > Rsync areturns with non-zero (code 20) exit code when the running service > is > stopped, so systemctl stop rsync.service will make the service to enter > failed > state and not stopped state. > > This is IMHO a bug in rsync when running as daemon. most if not all of > other > daemons return 0 exity code on SIGTERM. > > -- > Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the QA contact for the bug. > > _______________________________________ > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > > rsync mailing list > rsync@lists.samba.org > https://lists.samba.org/mailman/listinfo/rsync > >
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
