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