The following packages have been upgraded in the Cygwin distribution: * gzip 1.11
GNU gzip is a popular data compression program, developed to replace compress because of patents covering the LZW algorithm at the time, with better compression as a bonus. For more information see the project home pages: https://www.gnu.org/software/gzip/ https://sv.gnu.org/projects/gzip/ For changes since the previous Cygwin release please see below or read /usr/share/doc/gzip/NEWS after installation; for complete details see: /usr/share/doc/gzip/ChangeLog https://git.sv.gnu.org/gitweb/?p=gzip.git;a=log;h=refs/tags/v1.11 Noteworthy changes in release 1.11 (2021-09-03) [stable] * Bug fixes * Documentation improvements * Performance improvements * Infrastructure upgrades Noteworthy changes in release 1.10 (2018-12-29) [stable] * Changes in behavior Compressed gzip output no longer contains the current time as a timestamp when the input is not a regular file. Instead, the output contains a null (zero) timestamp. This makes gzip's behavior more reproducible when used as part of a pipeline. (As a reminder, even regular files will use null timestamps after the year 2106, due to a limitation in the gzip format.) * Bug fixes A use of uninitialized memory on some malformed inputs has been fixed. [bug present since the beginning] A few theoretical race conditions in signal handers have been fixed. These bugs most likely do not happen on practical platforms. [bugs present since the beginning] Noteworthy changes in release 1.9 (2018-01-07) [stable] * Bug fixes gzip -d -S SUFFIX file.SUFFIX would fail for any upper-case byte in SUFFIX. E.g., before, this command would fail: $ :|gzip > kT && gzip -d -S T kT gzip: kT: unknown suffix -- ignored [bug present since the beginning] When decompressing data in 'pack' format, gzip no longer mishandles leading zeros in the end-of-block code. [bug introduced in gzip-1.6] When converting from system-dependent time_t format to the 32-bit unsigned MTIME format used in gzip files, if a timestamp does not fit gzip now substitutes zero instead of the timestamp's low-order 32 bits, as per Internet RFC 1952. When converting from MTIME to time_t format, if a timestamp does not fit gzip now warns and substitutes the nearest in-range value instead of crashing or silently substituting an implementation-defined value (typically, the timestamp's low-order bits). This affects timestamps before 1970 and after 2106, and timestamps after 2038 on platforms with 32-bit signed time_t. [bug present since the beginning] Commands implemented via shell scripts are now more consistent about failure status. For example, 'gunzip --help >/dev/full' now consistently exits with status 1 (error), instead of with status 2 (warning) on some platforms. [bug present since the beginning] Support for VMS and Amiga has been removed. It was not working anyway, and it reportedly caused file name glitches on MS-Windowsish platforms.