From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Retry / Continue dialog appearing frequently in setup for dll updates
Date: Tue, 2 Aug 2022 09:05:27 -0400 [thread overview]
Message-ID: <9952869c-9bf4-8212-9dd0-1fb1631b045c@cornell.edu> (raw)
In-Reply-To: <CAFWoy7HZ3pQZzxvbgk4rijjdthdhydF6jYHq=tUVgEyhLLW8bw@mail.gmail.com>
On 7/31/2022 7:36 AM, Keith Christian wrote:
> On two different Windows 10 machines, I see the Retry/Continue dialog
> on numerous cygwin .dll files.
> These are the only cygwin processes extant while setup is running:
[...]
> Setup might benefit from the "Continue" option having a checkbox or
> separate button such as "Continue for all remaining" so that
> "Continue" wouldn't require the user to click "Continue" endlessly
> until all dll's are installed.
The standard advice is to shut down *all* Cygwin processes before running setup.
I don't see why we would want to make it easier for users to disregard that
advice.
> I could see only coreutils 8.32, no coreutils 9 versions, even with
> choosing Full, Test, etc. in setup.
Choose the "Full" or "Up To Date" view, search for coreutils, and click the
arrow at the right of the "New" column. You should see "9.0-1 (Test)" as one of
the available versions.
Ken
next prev parent reply other threads:[~2022-08-02 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 11:36 Keith Christian
2022-07-31 15:07 ` Jon Turney
[not found] ` <CAFWoy7GmW4wXd50c=wqh_618MMN8PHR2jWufZn_KSEQ26_jTaw@mail.gmail.com>
2022-08-03 19:52 ` Jon Turney
2022-08-02 13:05 ` Ken Brown [this message]
2022-08-02 16:13 ` Keith Christian
2022-08-04 12:37 ` Andrey Repin
2022-08-04 14:09 ` Keith Christian
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=9952869c-9bf4-8212-9dd0-1fb1631b045c@cornell.edu \
--to=kbrown@cornell.edu \
--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).