public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Cygwin x86 end-of-life
Date: Fri, 11 Nov 2022 20:45:06 +0100	[thread overview]
Message-ID: <72f286a1-7bea-d3ca-fbef-de55c15d9e28@towo.net> (raw)
In-Reply-To: <13518d55-4b3c-cefd-166d-d41ec7f1a70d@dronecode.org.uk>


Am 11.11.2022 um 17:16 schrieb Jon Turney:
> On 11/11/2022 15:50, Jon Turney wrote:
>>
>> As has previously been announced, Cygwin is dropping support for x86 
>> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit) 
>> Windows, and the forthcoming Cygwin 3.4 will be released for x86_64 
>> only.
>>
>> Concurrent with that, updates to x86 packages will be stopped, and 
>> the Cygwin x86 package repository will be archived.
>
> I plan to pause package uploads this coming Monday (2022-11-14), 
> before starting the re-organization of the package repository to make 
> this archive.
Although expected for a while, the exact date is now a very short-time 
announcement. Can we have a moratorium for a short while?

>
> When package updates resume (I don't have an ETA, but I expect it will 
> take a few days to attend to all the details), attempts to upload x86 
> packages will be rejected with an error.
>
>> (Instructions on the special steps needed to install from that 
>> archive will be forthcoming, once we've worked out what they are.)
>>
>> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please 
>> strongly consider moving to an x86_64 Cygwin installation.
>>
>> (If you have ARM hardware, we believe that x86_64 Cygwin works 
>> correctly using the x86_64 emulation in Windows 11)
>>
>> If you're one of the tiny percentage of Cygwin users using x86 Cygwin 
>> on a real x86 Windows OS, don't panic! The current installation will 
>> continue to run on your system. You just won't get any more updates.
>


  reply	other threads:[~2022-11-11 19:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cfc30991-0dd0-3308-9aca-df7cf81169aa@dronecode.org.uk>
2022-11-11 16:16 ` Jon Turney
2022-11-11 19:45   ` Thomas Wolff [this message]
2022-11-11 19:50     ` Achim Gratz
2022-11-11 20:02       ` Thomas Wolff
2022-11-12 16:08         ` Jon Turney
2022-11-12 16:58           ` Thomas Wolff
2022-11-13 13:58             ` Thomas Wolff
2022-11-13 16:43               ` Achim Gratz
2022-11-13 17:01                 ` Thomas Wolff
2022-11-13 17:07             ` Jon Turney
2022-11-13 19:17               ` Corinna Vinschen
2022-11-14 15:24     ` Andrew Schulman
2022-11-13 20:31   ` Brian Inglis
2022-11-14 16:25   ` Jon Turney
2022-11-14 17:18     ` Andrew Schulman
2022-11-14 20:16     ` Brian Inglis
2022-11-14 21:29       ` Jason Pyeron
2022-11-18 15:51         ` Jon Turney
2022-11-15 19:14     ` Erwin Waterlander
2022-11-28 13:08     ` Jon Turney
2022-11-21 12:45 Corinna Vinschen
2022-11-22 17:51 ` Brian Inglis
2022-11-22 21:07   ` Achim Gratz
2022-11-23 20:00     ` Brian Inglis

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=72f286a1-7bea-d3ca-fbef-de55c15d9e28@towo.net \
    --to=towo@towo.net \
    --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).