From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: upload with "previous"
Date: Sun, 24 May 2020 17:03:28 +0100 [thread overview]
Message-ID: <e83f4f63-0db2-c75d-0fbb-0a3715f95423@dronecode.org.uk> (raw)
In-Reply-To: <e5bfff8c-965c-1cf4-7e9d-ab824b6bfe14@dronecode.org.uk>
On 21/05/2020 20:58, Jon Turney wrote:
> On 21/05/2020 19:27, Thomas Wolff wrote:
>> I wanted to upload mintty 3.1.6 with a specific setup.hint containing
>> curr: 3.1.6
>> prev: 3.1.4
>> but got it wrong so the upload was "normal" instead.
>> I've now uploaded just the setup.hint (mintty-3.1.6-1.hint) and !ready
>> files manually. Will that work or should I repeat the complete upload?
>
> These 'curr' and prev' key are only valid in an override.hint file:
>
> https://cygwin.com/packaging-hint-files.html#override.hint
Correction: per [1], 'prev:' isn't actually valid in override.hint
anymore, since it didn't actually do anything much.
So all you are really saying here is 'curr: 3.1.6', which calm is
capable of working out anyhow, and will be wrong when the next version
is uploaded (and require you to remember to remove it then).
So, um, yeah.
[1] https://cygwin.com/pipermail/cygwin-apps/2020-March/039948.html
> (It's unclear how these should be interpreted if they were present with
> different values in the hints for different versions)
>
> However, in this case since you simply wish to withdraw 3.1.5-1, I'd
> suggest you use the provided mechanism to delete that version:
>
> https://cygwin.com/package-upload.html#deleting
next prev parent reply other threads:[~2020-05-24 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 18:27 Thomas Wolff
2020-05-21 19:58 ` Jon Turney
2020-05-24 16:03 ` Jon Turney [this message]
2020-05-21 20:08 ` Achim Gratz
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=e83f4f63-0db2-c75d-0fbb-0a3715f95423@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).