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.5-1
Date: Fri, 13 May 2022 14:32:53 +0200	[thread overview]
Message-ID: <20220513143253.2215409-1-corinna-cygwin@cygwin.com> (raw)

The following packages have been uploaded to the Cygwin distribution:

* cygwin-3.3.5-1
* cygwin-devel-3.3.5-1
* cygwin-doc-3.3.5-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 late 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 a bug that accessing UNC path mounted to a drive letter using
  SMB3.11 fails with error "Too many levels of symbolic links.".

- Fix a console bug that escape sequence IL/DL (CSI Ps L, CSI Ps M)
  does not work correctly at the last line.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-February/250736.html

- Fix a problem that ENABLE_INSERT_MODE and ENABLE_QUICK_EDIT_MODE
  flags are cleared if cygwin is started in console.

- Fix an issue that cmd.exe also is terminated along with the cygwin
  app started from the cmd.exe if the cygwin app is terminated by
  Ctrl-C.

- Fix deadlock caused when keys are typed in pty while a lot of text
  output.

- Fix a problem that the console mode for input is not set correctly
  when non-cygwin app is started with stdin redirected.
  Addresses:
  https://github.com/GitCredentialManager/git-credential-manager/issues/576

- Fix some problems such as:
   1) If output of non-cygwin app and input of cygwin app are connected
      by a pipe, Ctrl-C has to be sent twice to stop apps when the
      cygwin app does not read stdin at the moment.
   2) In cmd.exe started from cygwin shell, if output of non-cygwin
      app and input of cygwin app are connected by a pipe, Ctrl-C
      can never terminate the apps.

- Fix exit code when non-cygwin app is terminated by Ctrl-C.

- Fix a bug that the order of the console key inputs are occasionally
  swapped, especially when CPU load is high.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-February/250957.html

- Fix a problem that fsync() flushes the console input buffer unlike
  linux. fsync() should return EINVAL for special files such as tty.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-March/251022.html

- Fix a formatting problem in gmondump where all displayed addresses are
  mistakenly prefixed with "0x0x". Fix man pages for gmondump and ssp.

- Fix crash on pty master close in Windows 7.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-March/251162.html

- Avoid deadlock of non-cygwin pipe writer which occurs when the other
  cygwin pipe writers exist if the pipe is created by system account
  or the pipe creator is running as service.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-March/251097.html

                 reply	other threads:[~2022-05-13 12:37 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=20220513143253.2215409-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).