public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Ivan Gagis <igagis@gmail.com>
Subject: Re: mksetupini fails validating packages because curr is test
Date: Wed, 29 Nov 2017 16:52:00 -0000	[thread overview]
Message-ID: <3e13ae03-786f-6157-00a3-53e909495751@dronecode.org.uk> (raw)
In-Reply-To: <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

  reply	other threads:[~2017-11-29 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 15:07 Ivan Gagis
2017-11-29 16:52 ` Jon Turney [this message]
     [not found]   ` <CAL_02JC8t9TM6bRyrovCVJRv+pogdn+fNH7kv8ha016XZw0irA@mail.gmail.com>
2017-11-29 22:13     ` Jon Turney
2017-11-30  9:29       ` Ivan Gagis
2017-11-30 12:41         ` Jon Turney
2017-11-30 22:16           ` Ivan Gagis
2017-12-01 11:00             ` Jon Turney
2017-12-04 12:02               ` Ivan Gagis
2017-12-04 14:00                 ` Jon Turney
2017-12-04 16:57                   ` Ivan Gagis
2017-11-30 18:11         ` Wayne Davison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e13ae03-786f-6157-00a3-53e909495751@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=igagis@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).