public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin gzip Co-Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Test: gzip 1.12 (TEST)
Date: Sat, 09 Apr 2022 09:54:01 -0600	[thread overview]
Message-ID: <20220409095401.25169-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following test packages have been uploaded to the Cygwin distribution:

* gzip	1.12

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.

Please test this Base category utility as extensively as possible
(especially if you are a Cygwin package maintainer) as this package is
used in all installations. 
I have it locally installed so it is getting used by commands, scripts,
cron jobs, and cygport builds, and is getting frequent exercise
with no apparent issues so far.
If no issues are reported within a couple of weeks the package will be
upgraded to current stable.

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.12


Noteworthy changes in release 1.12 (2022-04-07) [stable]

* Changes in behavior

  'gzip -l' no longer misreports file lengths 4 GiB and larger.
  Previously, 'gzip -l' output the 32-bit value stored in the gzip
  header even though that is the uncompressed length modulo 2**32.
  Now, 'gzip -l' calculates the uncompressed length by decompressing
  the data and counting the resulting bytes.  Although this can take
  much more time, nowadays the correctness pros seem to outweigh the
  performance cons.

  'zless' is no longer installed on platforms lacking 'less'.

* Bug fixes

  zgrep applied to a crafted file name with two or more newlines
  can no longer overwrite an arbitrary, attacker-selected file.
  [bug introduced in gzip-1.3.10]

  zgrep now names input file on error instead of mislabeling it as
  "(standard input)", if grep supports the GNU -H and --label options.

  'zdiff -C 5' no longer misbehaves by treating '5' as a file name.
  [bug present since the beginning]

  Configure-time options like --program-prefix now work.


                 reply	other threads:[~2022-04-09 15:57 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=20220409095401.25169-1-Brian.Inglis@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=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).