From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: fish 2.5.0-1?
Date: Tue, 07 Feb 2017 20:24:00 -0000 [thread overview]
Message-ID: <39ff75f3-6922-d1b9-f5ed-8fe1a5ddc853@dronecode.org.uk> (raw)
In-Reply-To: <ee4k9cp9mp9jm9flafitt6gcl8isocc806@4ax.com>
On 07/02/2017 18:29, Andrew Schulman wrote:
>> On 07/02/2017 16:51, Marco Atzeri wrote:
>>> On 07/02/2017 17:49, Andrew Schulman wrote:
>>>> I uploaded fish 2.5.0-1 for x86 and x86_64 on Sunday, Feb. 5. I got a
>>>> confirmation notice from calm around noon EST. But it hasn't shown up in
>>>> any of the mirrors yet (at least, the 3 I looked at). Is there just a
>>>> delay, or some problem that needs to be resolved?
>>>
>>> it is there
>>> https://cygwin.com/packages/x86_64/fish/fish-2.5.0-1
>>
>> It seems that the file is there on the mirrors, but you also currently
>> have an override.hint for fish, which says
>>
>> prev: 2.3.1-2
>> curr: 2.4.0-1
>>
>> The test: stability label is never assigned automatically, so 2.5.0-1
>> isn't currently installable, as it never shows up in setup. Maybe this
>> is making you think that it's not on the mirrors?
>>
>> If you let me know if 2.5.0-1 is meant to be test: or curr:, I'll fix
>> this up.
>
> Hm, not sure why that's there. Yes, please remove it. 2.5.0-1 should be
> current, and 2.4.0-1 prev.
This seems to be ok now.
I have a vague recollection that I might have put the override.hint file
there to work around some other problem (keeping 2.3.1-2 rather than
2.4b1-1 as prev:?), if that's the case, apologies for the confusion.
next prev parent reply other threads:[~2017-02-07 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 16:49 Andrew Schulman
2017-02-07 16:51 ` Marco Atzeri
2017-02-07 18:08 ` Jon Turney
2017-02-07 18:29 ` Andrew Schulman
2017-02-07 20:24 ` Jon Turney [this message]
2017-02-08 1:16 ` Andrew Schulman
2017-02-07 18:09 ` Jon Turney
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=39ff75f3-6922-d1b9-f5ed-8fe1a5ddc853@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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).