From: Corinna Vinschen via Cygwin-announce <cygwin-announce@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] cygwin 3.3.6-1
Date: Mon, 05 Sep 2022 19:35:47 +0200 [thread overview]
Message-ID: <announce.20220905193547.2354458-1-corinna-cygwin@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygwin-3.3.6-1
* cygwin-devel-3.3.6-1
* cygwin-doc-3.3.6-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 an issue that command "cmd /c script -c cmd" crashes if it
is issued in console of Windows 7.
- Fix killpg failing because the exec'ing as well as the exec'ed
process are not in the pidlist for a brief moment.
Addresses: https://cygwin.com/pipermail/cygwin/2022-May/251479.html
- Fix mknod (64-bit only), whose definition didn't match its prototype.
Addresses: https://cygwin.com/pipermail/cygwin-developers/2022-May/012589.html
- Fix a regression that prevented Cygwin from starting if cygwin1.dll
is in the root directory.
Addresses: https://cygwin.com/pipermail/cygwin/2022-May/251548.html
- Handle setting very long window title correctly in console.
Addresses: https://cygwin.com/pipermail/cygwin/2022-June/251662.html
- Fix a bug of poll() that it returns event which is not inquired
if events are inquired in multiple pollfd entries on the same fd
at the same time.
Addresses: https://cygwin.com/pipermail/cygwin/2022-June/251732.html
- Fix a console problem that the text longer than 1024 bytes cannot
be pasted correctly.
Addresses: https://cygwin.com/pipermail/cygwin/2022-June/251764.html
- Fix a pty problem that pty failed to switch I/O pipe to that for
native apps if *.bat or *.cmd is executed directly from cygwin
shell.
Addresses: https://cygwin.com/pipermail/cygwin/2022-July/251993.html
- Fix a problem that prevented some symbolic links to /cygdrive/C,
/cygdrive/./c, /cygdrive//c, etc. from working.
Addresses: https://cygwin.com/pipermail/cygwin/2022-July/251994.html
- Fix a path handling bug that could cause a non-existing file to be
treated as the current directory.
Addresses: https://cygwin.com/pipermail/cygwin/2022-August/252030.html
- Fix a crash in newlocale.
Addresses: https://cygwin.com/pipermail/cygwin/2022-August/252043.html
reply other threads:[~2022-09-05 17: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=announce.20220905193547.2354458-1-corinna-cygwin@cygwin.com \
--to=cygwin-announce@cygwin.com \
--cc=cygwin@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).