From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: fish curr and prev are reversed
Date: Tue, 31 May 2016 11:08:00 -0000 [thread overview]
Message-ID: <7f955622-0cfb-7f10-2912-339b136a3918@dronecode.org.uk> (raw)
In-Reply-To: <20160531095409.GF24015@calimero.vinschen.de>
On 31/05/2016 10:54, Corinna Vinschen wrote:
> On May 31 04:32, Andrew Schulman wrote:
>> RIght now for fish, version 2.3b1-1 is current and 2.3.0-1 is prev. This is the
>> opposite of what I intended. I expected 2.3b1 to sort before 2.3.0.
>>
>> AFAIK the last setup.hint that I uploaded didn't include curr: or prev: lines,
>> so this looks to be what calm decided to do. Can someone please fix it?
>
> Did you see the calm warning? For some reason the 64 bit version is
> missing debuginfo packages later than 2.2.0-3.
Unfortunately, because this is an error in the state of the release
area, and not with an upload, calm isn't smart enough to known which
package maintainer to tell about this.
> ERROR: package 'fish-debuginfo' stability 'curr' selects non-existent version '2.3b1-1'
> ERROR: package 'fish-debuginfo' stability 'prev' selects non-existent version '2.3.0-1'
> ERROR: existing x86_64 package set has errors
next prev parent reply other threads:[~2016-05-31 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:33 Andrew Schulman
2016-05-31 9:03 ` Achim Gratz
2016-05-31 9:11 ` Corinna Vinschen
2016-05-31 10:46 ` Achim Gratz
2016-05-31 10:51 ` Corinna Vinschen
2016-05-31 12:13 ` Andrew Schulman
2016-05-31 9:54 ` Corinna Vinschen
2016-05-31 11:08 ` Jon Turney [this message]
2016-05-31 11:06 ` Jon Turney
2016-05-31 12:20 ` Andrew Schulman
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=7f955622-0cfb-7f10-2912-339b136a3918@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).