public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: coreutils 9.0 (TEST)
Date: Tue, 19 Jul 2022 22:22:00 -0600	[thread overview]
Message-ID: <9cbfe30f-7022-e1f4-cc8b-8f2c0cf2aa78@SystematicSw.ab.ca> (raw)
In-Reply-To: <74c4b978-113f-be42-43a1-66d7c61ffac1@SystematicSw.ab.ca>

On 2022-07-19 21:03, Brian Inglis wrote:
> On 2022-07-19 15:06, Ken Brown wrote:
>> On 7/19/2022 3:54 PM, Brian Inglis wrote:
>>> On 2022-07-19 12:00, Ken Brown wrote:
>>>> On 7/19/2022 1:07 PM, Brian Inglis wrote:
>>>>> Setup still shows coreutils 9.1 as test, but it should *NOT* be 
>>>>> installed by anyone.
>>>>
>>>> Then shouldn't you remove it?  And you could also upload an 
>>>> override.hint file with a "replace-versions" line for the sake of 
>>>> people who have already installed it.
>>>
>>> I tried various measures and thought override.hint with 
>>> replace-versions: 9.1-1 was there.
>>
>> It is there, so whatever you did worked.  But that doesn't prevent 
>> people from installing 9.1-1.  If someone installs 9.1-1, then the 
>> *next* time they run setup they'll get the suggestion to downgrade it. 
> 
> I previously asked about reverting the release, and did as suggested.
> 
>> If you really don't want anyone to install 9.1-1, you should remove it.
> 
> How do I get calm and setup to do that in the release area?

I have manually uploaded empty:

x86{,64}/release/coreutils{,/coreutils-debuginfo}/-coreutils-9.1-1.{,-src}.{hint,tar.xz}

and created !ready files in:

x86{,64}/release/coreutils{,/coreutils-debuginfo}/

which appears to have moved the files to the vault(/Attic) and dropped 
the entries from setup.ini

That seems like a job for a cygport command like remove/vault! ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      reply	other threads:[~2022-07-20  4:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  3:38 Cygwin coreutils Co-Maintainer
2022-07-19  1:50 ` Keith Christian
2022-07-19  2:47   ` René Berber
2022-07-19 11:34     ` Keith Christian
2022-07-19 16:50       ` René Berber
2022-07-19 16:55         ` René Berber
2022-07-31 22:45         ` Keith Christian
2022-07-19 17:07       ` Brian Inglis
2022-07-19 18:00         ` Ken Brown
2022-07-19 19:54           ` Brian Inglis
2022-07-19 21:06             ` Ken Brown
2022-07-20  3:03               ` Brian Inglis
2022-07-20  4:22                 ` Brian Inglis [this message]

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=9cbfe30f-7022-e1f4-cc8b-8f2c0cf2aa78@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@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).