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.4-1
Date: Mon, 31 Jan 2022 13:04:59 +0100	[thread overview]
Message-ID: <20220131130459.1400457-1-corinna-cygwin@cygwin.com> (raw)

The following packages have been uploaded to the Cygwin distribution:

* cygwin-3.3.4-1
* cygwin-devel-3.3.4-1
* cygwin-doc-3.3.4-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 a bug in fhandler_dev_clipboard::read() that the second read
  fails with 'Bad address'.
  Addresses: https://cygwin.com/pipermail/cygwin/2021-December/250141.html

- Convert UNC path prefix back to drive letter in symlink_info::check().
  This solves the following issues:
  Addresses: https://cygwin.com/pipermail/cygwin/2021-November/250087.html
             https://cygwin.com/pipermail/cygwin/2021-December/250103.html

- Fix a bug in pty code that input is wrongly sent to io_handle_nat
  rather than io_handle while neither read() nor select() is called
  after the cygwin app is started from non-cygwin app.
  Addresses: https://cygwin.com/pipermail/cygwin-patches/2021q4/011587.html

- Avoid a crash when NtQueryInformationProcess returns invalid handle data.
  Addresses: https://cygwin.com/pipermail/cygwin-patches/2021q4/011611.html

- Ignore INHERIT ACEs when reading the DACL of non-directory files.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250363.html

- Fix an "Invalid argument" problem in posix_spawn on i686.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250453.html

- Fix handling of AAAA records in Cygwin resolver code using native
  windows calls.  Also fix various bugs in the resolver.

- Fix a problem creating a dir "foo", if a file (but not a Cygwin symlink)
  "foo.lnk" already exists.
  Addresses: https://github.com/msys2/msys2-runtime/issues/81

- Fix double free for archetype, which is caused when open() fails.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250518.html

- Fix a permission problem when writing DOS attributes on Samba.
  Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250629.html


                 reply	other threads:[~2022-01-31 12:07 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=20220131130459.1400457-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).