public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygwin 3.3.3-1 [with DEPRECATION NOTES]
Date: Fri, 03 Dec 2021 17:48:03 +0100	[thread overview]
Message-ID: <20211203174803.1446397-1-corinna-cygwin@cygwin.com> (raw)

The following packages have been uploaded to the Cygwin distribution:

* cygwin-3.3.3-1
* cygwin-devel-3.3.3-1
* cygwin-doc-3.3.3-1

==========================================================================
                   IMPORTANT DEPRECATION NOTES
==========================================================================

- Cygwin 3.3 is the LAST major version supporting

  - Windows Vista
  - Windows Server 2008

- Cygwin 3.3 is the LAST major version supporting 32 bit installations.

  If you're using 32 bit Cygwin in WOW64 on 64 bit machines, consider
  to move to a real 64 bit Cygwin installation in the next couple of
  months.

  If you're using 32 bit Cygwin on real 32 bit hardware or on WOW64 on
  ARM64, don't be alarmed.  The current installations including all
  Cygwin 3.3.x versions will continue to run on your system.  You just
  wont get any more updates starting with Cygwin 3.4.0.

- Cygwin 3.4, which will probably be release at some point in 2022,
  will be the LAST version supporting

  - Windows 7
  - Windows Server 2008 R2
  - Windows 8
  - Windows Server 2012

There are no plans to deprecate support for 64 bit systems starting with
Windows 8.1 / Windows Server 2012 R2 any time soon.

==========================================================================

Bug Fixes
---------

- Fix issue that new pipe code doesn't handle size zero pipe which
  may be created by non-cygwin apps.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249844.html

- Make sure that "X:" paths are not handled as absolute DOS paths in
  fstatat and other ...at calls.  "X:/" still is handled as absolute
  path.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249837.html

- Fix showing DLL version info from native Windows tools.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249867.html

- Handle Unicode surrogate pairs in console. Cygwin console does not
  handle surrogate pairs correctly at the moment.  Fix issue that
  running bash in Windows Terminal and inserting an emoji does not
  work as expected.
  Addresses: https://github.com/git-for-windows/git/issues/3281

- Fix long-standing problem that fchmod or facl on newly created files
  screw up the DOS file attributes.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249909.html

- Fix issue that pipe read()/write() occasionally returns a garbage
  length when NtReadFile/NtWriteFile returns STATUS_PENDING in non-
  blocking mode.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249910.html

- Fix two bugs in raise(2).
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249973.html

- Fix regression in printf introduced with Cygwin 3.3.2.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/249930.html

                 reply	other threads:[~2021-12-03 16:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211203174803.1446397-1-corinna-cygwin@cygwin.com \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-announce@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).