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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <a7c24330-21d1-42aa-bc3b-db9620ac77d8@dronecode.org.uk>
References: <CAL_02JBn=m9z9d6cjJ==-wc1_k6iG=0rmRR4VqiOuB0vfAkovA@mail.gmail.com> <3e13ae03-786f-6157-00a3-53e909495751@dronecode.org.uk> <CAL_02JC8t9TM6bRyrovCVJRv+pogdn+fNH7kv8ha016XZw0irA@mail.gmail.com> <a7c24330-21d1-42aa-bc3b-db9620ac77d8@dronecode.org.uk>
From: Ivan Gagis <igagis@gmail.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.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"

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.turney@dronecode.org.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