From: Jon Turney <jon.turney@dronecode.org.uk>
To: Fergus Daly <fergusd84@outlook.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin x86 end-of-life instructions worked really well
Date: Sun, 12 Feb 2023 16:35:39 +0000 [thread overview]
Message-ID: <3230b178-73aa-2a8d-3afb-81002eccd9f0@dronecode.org.uk> (raw)
In-Reply-To: <DB6P18901MB0055D44D1E9AA1F9303E15BBA4DE9@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
On 10/02/2023 17:27, Fergus Daly via Cygwin wrote:
> Just to say: the instructions at
> https://cygwin.com/pipermail/cygwin-announce/2022-November/010810.html
> work really well.
You're welcome.
> I used the following single command at the Command Prompt:
> "setup-x86-2.924.exe --allow-unsupported-windows
> --site http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/2022/11/23/063457
> -P package1,package2,..,packageN"
> (all on one line) to recover completely my original Cygwin32 platform
> (being Base + list of required additions).
> PS1: If you visit this page there is an intrusive word "option" in the instruction
> .. '--allow-unsupported-windows option --site circa_URL' ..
Yes, there's an unfortunate typo in that mail. I've since fixed it on
the installer page [1], but I am lacking a time machine to fix the
original email :)
[1] https://cygwin.com/install.html#unsupported
> PS2: Can't actually remember where or how I got the required executable
> setup-x86-2.924.exe
If you didn't have it already, it's linked a bit a bit further down that
page, after "You have been warned... if you really need a 32-bit Cygwin...".
prev parent reply other threads:[~2023-02-12 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 17:27 Fergus Daly
2023-02-12 16:35 ` Jon Turney [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=3230b178-73aa-2a8d-3afb-81002eccd9f0@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=fergusd84@outlook.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).