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:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=tiDLD+op/Xcw+7hC NTvpKrGtCo/Zk2F79IOrtPmdlA0gwm93hn6PrHCuWO8d37wGhNPfrZTEDIjfJCwa 1aYR8vf3J00l/Ke4XxFKGmkMeG2j7boZFJOZqla7T6246d8sKqztYOyNDIcck8ug SY6PGF7YEXicNxxAyoJV6YlfOc0= 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:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=P3tDPW1M+z3LK7OHva+cFN IMBdE=; b=rA4NqUMOQRZ0DBCNvBiZpBtTcOA+cjs4oRJghrIBW4bZlPmAFNYHNN psDMG18MhhOxKiwW+9EQetAWebiJAqA0UU+uSPiHhjEVfcWMLqL4p3+fAiubs8zP qOClqLLZAMOLzU6zvqdbfhqEBm+Qq859rzCP1weY3/ua1qIMyq8es= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-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=Hx-languages-length:1593, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com X-ME-Sender: Subject: Re: mksetupini fails validating packages because curr is test To: The Cygwin Mailing List References: <3e13ae03-786f-6157-00a3-53e909495751 AT dronecode DOT org DOT uk> Cc: Ivan Gagis From: Jon Turney Message-ID: Date: Wed, 29 Nov 2017 22:13:43 +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 On 29/11/2017 21:34, Ivan Gagis wrote: > What is that timestamp? Is it when the package was uploaded? Sorry, by timestamp, I just mean the mtime of the archive file. > Then it should not be possible, because lower version definitely was > uploaded earlier than higher version package. > > Where are those timestamps kept? Hint files does not contain any > timestamp and setup.ini only has its global timestamp, but not > per-package timestamps. > > Do you have any suggestion of how to fix this? Assuming you've found a bug, I need some more details to enable me to reproduce it, before I can fix it... > 2017-11-29 18:52 GMT+02:00 Jon Turney: >> On 29/11/2017 15:06, Ivan Gagis wrote: >>> >>> I have an overlay cygwin repo where I publish my packages. >>> >>> Recently I started getting errors from mksetupini script: >>> >>> " >>> mksetupini: package 'mypackage' version '0.4.38-1' is most recent >>> non-test version, but version '0.4.43-1' is curr: >>> mksetupini: package set has errors, not writing setup.ini >>> " >>> >>> there was no such errors before. And I don't have "test:" in any hint >>> files of my packages, so no I dea why it thinks that some versions are >>> non-test and curr is test? >> >> >> It's not saying any versions are test. >> >>> Can you explain what this actually means? >> >> >> "most recent" means "latest timestamp" >> >> So this is telling you that 0.4.38-1 is the non-test version which has the >> most recent timestamp, but 0.4.43-1 is curr: (because it's the highest >> non-test version) -- 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