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: Federico Kircheis <federico.kircheis@gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: neomutt-20191102-1
Date: Wed, 13 Nov 2019 16:47:00 -0000	[thread overview]
Message-ID: <80477246-6b36-f32e-00f4-6cf633fff404@dronecode.org.uk> (raw)
In-Reply-To: <877e46p90a.fsf@Rainer.invalid>

On 11/11/2019 18:23, Achim Gratz wrote:
> Federico Kircheis writes:
>> Now version 20191111 is out, and calm notifies through and error that
>> this version is older than the current.

This seems to be working as intended, as it's notifying you of an actual 
problem.

>> How can I/we fix this issue?

Sorry, this isn't well documented by [1].

This check can be disabled for a package by adding a 'disable-check: 
curr-most-recent' line to override.hint (creating that file if necessary)

> One way would be to make the 201922 version a "test" version, then after
> you've uploaded the 20191111 version you can remove it.

But that's not sufficient, as people who have already installed 
20191122-1 won't get 'downgraded' by setup (since 20191122  > 20191111)

So a 'replace-versions: 20191122-1' line in override.hint is also needed.

Unfortunately, due to setup limitations, that can't name a version 
that's also available to install, so that version also needs to be removed.

Anyhow, I did all that, so things should be good now.

[1] https://cygwin.com/packaging-hint-files.html#override.hint

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
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:[~2019-11-13 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 10:10 Federico Kircheis
2019-11-11 12:44 ` Federico Kircheis
2019-11-11 18:23   ` Achim Gratz
2019-11-13 16:47     ` Jon Turney [this message]
2019-11-13 18:29       ` Federico Kircheis

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=80477246-6b36-f32e-00f4-6cf633fff404@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=federico.kircheis@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).