From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: Which rsync version is current?
Date: Wed, 27 May 2020 16:19:10 -0400 [thread overview]
Message-ID: <4fc30994-90eb-43cb-4390-c94b81ceb22b@cornell.edu> (raw)
In-Reply-To: <CANV9t=T6aMKV1UWWKAyc7pYFwKnDGdZa2ibBTzDcLAjsBaZZdA@mail.gmail.com>
[Adding the rsync maintainer to the Cc in case he wants to add something.]
On 5/27/2020 3:34 PM, Bill Stewart wrote:
> On Wed, May 27, 2020 at 1:20 PM Andrey Repin wrote:
>
>>> When I run rsync --version, I see this:
>>>
>>> rsync version 3.2.0dev protocol version 31
>>>
>>> However the Cygwin Setup program says that my rsync is current and is
>>> listed as this version:
>>>
>>> 3.1.3+20200429+gitf7746d0-1
>>>
>>> rsync.samba.org says the current version is 3.1.3.
>>>
>>> So...what's actually the latest? What's the difference between these?
>>
>> Run `which rsync` to see which one is responding to you.
>>
>> 3.2-dev is likely a snapshot from ongoing development branch.
>
> `which rsync` outputs
>
> /usr/bin/rsync
>
> as expected.
>
> What I am saying is that the Setup program says the installed version
> is 3.1.3+20200429+gitf7746d0-1.
The version number shown by setup indicates that the maintainer built the
package from a snapshot of the upstream git repository rather than from a stable
release. The maintainer chose this version number, presumably to indicate that
the snapshot was made on 2020-04-29 after git commit f7746d0.
> For that installed version, `rsync --version` says the version is 3.2.0dev
That version number is determined by the upstream rsync developers, and it
indicates that the build is based on a snapshot of the development branch for a
future 3.2.0 release. (This is what Andrey was saying.)
The latest stable release, 3.1.3, is two years old. I'm sure Jari had good
reasons for wanting to make a more recent version available.
Ken
next prev parent reply other threads:[~2020-05-27 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:35 Bill Stewart
2020-05-27 19:16 ` Andrey Repin
2020-05-27 19:34 ` Bill Stewart
2020-05-27 20:19 ` Ken Brown [this message]
2020-05-27 21:02 ` Bill Stewart
2020-05-28 2:58 ` Marco Atzeri
2020-05-28 13:48 ` Bill Stewart
2020-05-27 19:27 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fc30994-90eb-43cb-4390-c94b81ceb22b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=jari.aalto@cante.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).