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=HPcN
	8jf8QftxRAt0EHPpBzyawU7YSuwY/i3SqI+ccnjbDC0ItekrD3Q/yoVcFoujCGyU
	AlY03vxJsDLmIgBr7VUIliPWpN0K8AMpwoQxthhuFIObgr/1njHTkI/WpkDm+t8M
	sKHgVQqhvi82ayQ34hu8ydWf4XbvZ2t2F707slU=
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=0LFuBW3FNT
	4b3h+DeJ+KumCr0Kw=; b=FgL/zNKZ7wSaQKzT/T+BXi+N81GFOYZbSyD5dI4V6N
	xr5Y/V2AYshp0zpjdIwrokWtJC3uLRgdBaVEuEfgtPo6OR7p1iGEAdMAckWL7Xmp
	38zNIrMF2XD1x365kqgQmMq39QaE6S1jsgGpGxHho+EEoEGJdCp6fgto8fFiIHPr
	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=HX-Received:Thu
X-HELO:	mail-lf0-f53.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=zq6S+HwgP2ywVyt5N+LhLqjEYL3iTmI6oGZEL/Ag/pQ=; b=uUHEN7r4A5axAoCF0Edgs8N13eZfAS1XiDmz5OOg/ay50354cy3hiukJhOxH8Z8zhf H3IaE0+3snp+eRuNonvcXnZCsDM/gIL6pEOWArZTbuFYSxw4VPZK2oeNmz2iBsSooNbf cOL3sW5uKY0mLP+AcBIi/GaJ+cTWQqIXZDHSYYR3/S6acwULG9zXVMt5EjYrcAllBE0O livZwJ/arhTGWcSVymQuZapPjx7KOEMA7orNp9yTpljiuIUag4EPr1ZTWKFw9/3yISpk WfJor9bMvPb0fpQmFPjzqeCqUSRqN9Myf6XgSKnc0PJDP2EMgnatUAY3j5MN3xUeUt+F vCVQ==
X-Gm-Message-State:	AJaThX5jD+dPWeKMMua+koINRSrm5ZoUPq+JXEssZxJwhwoq3KB9geZ7 5RMZbPBjJRq4budNc4C3O0OMX2l8C7wrjJnPcBw=
X-Google-Smtp-Source:	AGs4zMbBuX8+3LpPWF3SBxo5ic4neQz6LPwwgq1ilSffSqtounDwbet4KWZNkuGvIO38M8lhThm397yd77GMW7F8aRs=
X-Received:	by 10.25.150.137 with SMTP id y131mr2251376lfd.91.1512034137273; Thu, 30 Nov 2017 01:28:57 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<a7c24330-21d1-42aa-bc3b-db9620ac77d8@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>
From:	Ivan Gagis <igagis AT gmail DOT com>
Date:	Thu, 30 Nov 2017 11:28:56 +0200
Message-ID:	<CAL_02JCCmg4S03+Z1W_ADX0rR4nqxXcM0gjqhR07g56HNhQwkg@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>
X-IsSubscribed:	yes

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.

But why is this check of mtime needed at all? Isn't version number
enough for tracking earlier-later files?

Br,
Ivan


2017-11-30 0:13 GMT+02:00 Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>:
> 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

- Raw text -