X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type; q=dns; s=default; b=M5xV
	DtTKR9MJoB9asvhgr/E+XScA8UqnDh5nRqWsKROLUs787BVsplWImhrDV+Vci2MZ
	dApuvwlcYobKWDc/O7d/Kay88iHgQp3DQGg40G6LOf5M+kb2n7MqxnIJhDsUouLB
	dtIiq2wFwB12JCdqjt4wuYkeK+W9NcZQ26JyM3Q=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type; s=default; bh=y4xo6Wivyz
	B9x4sanND1EOyyjc0=; b=GwCfZP52K8kbp2F/J/vYyEVCS8+H0p4cdtWd3WKJ7L
	zl7y6OXAXFcCSPT3k2/k2qY/MV9fP0hOg5TDP9RhgHQkVtoF9wl7xDRsqHIxtZPt
	lr25/ilVNDXFErxlk3E3Cg1rvxEpQ9DCQPRlfliZ/myMTaN64VdKHSBoVrd9zAKX
	I=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=Maybe
X-HELO: mail-lf0-f44.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=GBW9Y9Nc+qd06xADQ0+a/V7Sd5QHTusW5GmuOl44wp8=;        b=W0O/faj+rZltxL2laUpSPuuPzsuf7FfGgzrpkZ9xFQFwbmohGAyyKykPTRX+IQf/5O         A8PHg4YzreDuYcFq74ucdL7IECZjt0gQjkGjgV2YiNBCl44TPME4hyepqCrflmCKNFBy         C0bfS647xP5cS21ibXrC5sjsRZ2LK1DRpun/EXQhgbXg0Xrkb3sqVQ1GNitvupr9eXGi         7IL4dIObwyWre6AkbjOCah66mFV4+tEgjX6nGGqtdkWW4WEGyDIjUdXQQ81V77z94/xh         AHoQDcDaa60A69uIJN141gmW5QhgK6jwB8uR25zth5D9azzIZ0SETeEmRp8Aughz1Gtf         VyEQ==
X-Gm-Message-State: AJaThX7ASMrn9e2H2UKo/+lLnJ+Oj+kze7+FbBeEvaSV/H7MV+o9fyGO	P4+gDcORoi6J4ln42Vn9wgK8EZtf44iZKeHAtOo=
X-Google-Smtp-Source: AGs4zMZwPY5DjqtGtW0gTJ6KqMv1BboMV5tK7MW6/20wWzB8oom1fVJJlixe/HvCUymShy6VuoO4Fjmd+nu4mZvFyl8=
X-Received: by 10.25.115.23 with SMTP id o23mr3655758lfc.164.1512080204392; Thu, 30 Nov 2017 14:16:44 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <8690f394-94f0-58ad-8a6b-8067edabc9d5@dronecode.org.uk>
References: <CAL_02JBn=m9z9d6cjJ==-wc1_k6iG=0rmRR4VqiOuB0vfAkovA AT mail DOT gmail DOT com> <3e13ae03-786f-6157-00a3-53e909495751 AT dronecode DOT org DOT uk> <CAL_02JC8t9TM6bRyrovCVJRv+pogdn+fNH7kv8ha016XZw0irA AT mail DOT gmail DOT com> <a7c24330-21d1-42aa-bc3b-db9620ac77d8 AT dronecode DOT org DOT uk> <CAL_02JCCmg4S03+Z1W_ADX0rR4nqxXcM0gjqhR07g56HNhQwkg AT mail DOT gmail DOT com> <8690f394-94f0-58ad-8a6b-8067edabc9d5 AT dronecode DOT org DOT uk>
From: Ivan Gagis <igagis AT gmail DOT com>
Date: Fri, 1 Dec 2017 00:16:43 +0200
Message-ID: <CAL_02JCSUXQ_gLbdKSxNaNXaDkWMKmgY_ntG-vjpchM2GpWT-w@mail.gmail.com>
Subject: Re: mksetupini fails validating packages because curr is test
To: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Cc: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

Hi Jon,

Thanks for prompt actions!

I think no need to package it separately for testing, just release it
to cygwin repo.

Yes, I understand that there always is a human factor, this is why I
do all my building, version bumping up and deployment automatically by
scripts, so this check seems unnecessary in my case and good that it
can be turned off now.

Br,
Ivan

2017-11-30 14:41 GMT+02:00 Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>:
> On 30/11/2017 09:28, Ivan Gagis wrote:
>>
>> I use git repository on github to store the files. And to update it I
>> clone the repo, run mksetupini and then commit and push.
>> So, I'm not sure what actually is going on with mtime of the files
>> there. Perhaps git messes up the mtime of cloned files.
>
>
> Yes, a git checkout will have the mtime of the checkout.
>
> I've pushed an update to the calm repo with these changes:
>
> - mksetupini and calm now exit with non-zero exit status on an error
> - Fixes a bug where equal mtime was considered newer
> - Adds 'mksetupini --disable-check=curr-most-recent' option to turn off this
> check
>
> Do I need to package this for you to test it?
>
>> But why is this check of mtime needed at all? Isn't version number
>> enough for tracking earlier-later files?
>
>
> Maybe this doesn't make much sense in the context of mksetupini, but this is
> a useful check for calm to make.
>
> People make mistakes.
>
> People also forget the subtleties of how version numbers sort and upload
> versions which aren't greater than the current version, when they think they
> are...

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple