public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Which rsync version is current?
Date: Thu, 28 May 2020 04:58:07 +0200	[thread overview]
Message-ID: <bdf27a75-daca-9254-e548-0b368a2bb48f@gmail.com> (raw)
In-Reply-To: <4fc30994-90eb-43cb-4390-c94b81ceb22b@cornell.edu>

On 27.05.2020 22:19, Ken Brown via Cygwin wrote:
> [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:
>>
>>
>> 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.
> 

the main reason to put the date in the version is
to assure that subsequent releases from git repository
will be considered higher by setup and offered as "New"
package

Using only the git tag you can not reach the scope
these are the latest commits on the Rsync code
and we can not say from the tag alone which is the latest

  $ git log --oneline |head
8809f65b A couple minor tweaks.
5710d2fe Simplify the capabilities array.
bcb0a24a Convert NEWS & OLDNEWS into .md files.
96ed96da Fix the parsing of the --version capabilities.
8ad2ca9a Install yodl for the CI builds.
23a37eca Get indent right.
47bae3ab Improve output of capabilities in --version list.
dff9dd56 Remove xxhash from capabilities list.
7182508a Fix a couple deb names.
cb0fe9e1 Improve CI setup.

I see the maintainer have tested his
choice of f7746d0 and he saw no reason to pack
the older 3.1.3

specially as 3.1.3 was NOT building under cygwin
https://bugzilla.samba.org/show_bug.cgi?id=14365

Regards
Marco


  parent reply	other threads:[~2020-05-28  2:58 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
2020-05-27 21:02       ` Bill Stewart
2020-05-28  2:58       ` Marco Atzeri [this message]
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=bdf27a75-daca-9254-e548-0b368a2bb48f@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).