This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: mksetupini fails validating packages because curr is test
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Cc: Ivan Gagis <igagis at gmail dot com>
- Date: Wed, 29 Nov 2017 16:52:15 +0000
- Subject: Re: mksetupini fails validating packages because curr is test
- Authentication-results: sourceware.org; auth=none
- References: <CAL_02JBn=m9z9d6cjJ==-wc1_k6iG=0rmRR4VqiOuB0vfAkovA@mail.gmail.com>
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