From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60426 invoked by alias); 30 Nov 2017 12:41:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 60417 invoked by uid 89); 30 Nov 2017 12:41:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=checkout, Hx-languages-length:1136, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 30 Nov 2017 12:41:50 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B33E920C2C; Thu, 30 Nov 2017 07:41:47 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 30 Nov 2017 07:41:47 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-179-113-49.range86-179.btcentralplus.com [86.179.113.49]) by mail.messagingengine.com (Postfix) with ESMTPA id 3CFDB24495; Thu, 30 Nov 2017 07:41:47 -0500 (EST) Subject: Re: mksetupini fails validating packages because curr is test To: cygwin@cygwin.com References: <3e13ae03-786f-6157-00a3-53e909495751@dronecode.org.uk> Cc: Ivan Gagis From: Jon Turney Message-ID: <8690f394-94f0-58ad-8a6b-8067edabc9d5@dronecode.org.uk> Date: Thu, 30 Nov 2017 12:41:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-11/txt/msg00306.txt.bz2 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