From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Revert coreutils 9.1 to test 8.32 to curr stable
Date: Tue, 7 Jun 2022 10:39:11 +0100 [thread overview]
Message-ID: <0b3c6d2a-ed24-7c58-be16-0a13adecbc7c@dronecode.org.uk> (raw)
In-Reply-To: <121ccc64-bb8e-30c1-2fba-b76920545a21@SystematicSw.ab.ca>
On 07/06/2022 00:33, Brian Inglis wrote:
> Verified below issue with coreutils 9.1 promoted last night to stable!
> Problem does not occur in 8.32, so can we please revert coreutils 9.1 to
> test and restore 8.32 to stable.
> Or is there some process by which I can do so?
You seem to have figured this out, but FTR:
* Remove [1] or re-upload [2] the package with test: added to hints
* Upload an override.hint with replace-versions: [3]
Note that due to the way the depsolver works, replace-versions: doesn't
do anything if the package would still be chosen to install.
(calm tries to warn about that, but it seems you've tripped over a bug
where it doesn't take test: into consideration and warns when it shouldn't)
[1] https://cygwin.com/package-upload.html#deleting
[2] Re-uploading a package with the same (or missing!) archives, but
modified hints is currently allowed for historical reasons
[3] https://cygwin.com/packaging-hint-files.html#override.hint
next prev parent reply other threads:[~2022-06-07 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220521145633.53343-1-Brian.Inglis@SystematicSW.ab.ca>
[not found] ` <CAK-n8j6kmto82kLgtk4+zajY9trjhhQG=U2BdjiScbMa91-mZg@mail.gmail.com>
2022-06-06 23:33 ` Brian Inglis
2022-06-07 9:24 ` Brian Inglis
2022-06-07 9:39 ` Jon Turney [this message]
2022-06-07 16:48 ` Brian Inglis
2022-06-07 18:48 ` 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=0b3c6d2a-ed24-7c58-be16-0a13adecbc7c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--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).