From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] gzip: Update to version 1.15
Date: Tue, 22 Sep 2026 19:24:07 +0200 [thread overview]
Message-ID: <20260922172417.3447503-6-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260922172417.3447503-1-adolf.belka@ipfire.org>
- Update from version 1.14 to 1.15
- No change in rootfile
- Changelog
1.15
** Bug fixes
gzip no longer can mistakenly remove the wrong file if some other
process simultaneously renames a gzip destination's ancestor.
[bug present since the beginning]
gzip -d no longer rejects PKZIP signatures, local header, and data
descriptors. These can appear in well-formed streamed zip files.
[bug present since the beginning]
gzip diagnostics now quote file names containing unusual characters.
[bug present since the beginning]
A use of uninitialized memory on some malformed inputs has been fixed.
[bug present since the beginning]
A buffer overflow has been fixed when decompressing an .lzh file
after decompressing a .Z file.
[bug present since the beginning]
When decompressing an .lzh file, the output is no longer corrupted
when an internal bit buffer is not properly cleared.
[bug present since the beginning]
When decompressing an .lzh file after another .lzh file, the output is
no longer corrupted by the previous file's decoding table.
[bug present since the beginning]
gzip --synchronous no longer fails to synchronize unreadable parent
directories on platforms like GNU/Linux that have O_PATH, or to
synchronize any parent directories on platforms like FreeBSD that
have O_SEARCH but not O_PATH.
[bug introduced in gzip-1.7]
On old-fashioned or limited platforms lacking mktemp, gzexe, zdiff
and znew no longer have a race when creating a temporary file.
[bug present since the beginning]
** Changes in behavior
gzip no longer insists on the "C" locale; instead, it follows the
typical practice of using the locale specified by the environment.
This change, which is needed for file name quoting, can affect the
format of floating-point numbers output by gzip's -l and -v options.
Diagnostics are still in English, though.
gzip -l now reports "-Inf%" instead of "0.0%" for the infinite
compression ratio of an empty file.
znew's -P option is now ignored, with a warning. It was present
only to improve performance, and its implementation had too many
bugs to be worth supporting.
** Platforms no longer supported
The following platforms (or earlier) are no longer supported because
their old multibyte libraries do not work well enough: FreeBSD 4.11
(2005), HP-UX 11.00 (1997), Minix 3.1.8 (2010), MS-Windows 8.1
(2013) via mingw without UCRT.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/gzip | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/gzip b/lfs/gzip
index 8f036063d..db02cba12 100644
--- a/lfs/gzip
+++ b/lfs/gzip
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2026 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 1.14
+VER = 1.15
THISAPP = gzip-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -49,7 +49,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 32f7241bd9f3b7f73a59905a5bc9abf4e360e787f692cbb00ad28d48abee52744846d10c07ce2f7aaa3e66bc4b6ab9cd4f1b8e98854bb7d1ec010ae0d5146932
+$(DL_FILE)_BLAKE2 = efa81df3df766502c5ffde551570b568c73d3b2ad0b2c76bd79b0ed5cea4deb5e0a3d803b942a078efdc4df9cde355863aadc51752498a9e7dec8737be559850
install : $(TARGET)
--
2.55.0
next prev parent reply other threads:[~2026-09-22 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:24 [PATCH] bash: Update to version 5.3 patch-20 Adolf Belka
2026-09-22 17:24 ` [PATCH] core205: Ship bash Adolf Belka
2026-09-22 17:24 ` [PATCH] core205: Ship gzip Adolf Belka
2026-09-22 17:24 ` [PATCH] core205: Ship less Adolf Belka
2026-09-22 17:24 ` [PATCH] core205: Ship readline Adolf Belka
2026-09-22 17:24 ` Adolf Belka [this message]
2026-09-22 17:24 ` [PATCH] harfbuzz: Update to version 14.5.0 Adolf Belka
2026-09-22 17:24 ` [PATCH] less: Update to version 710 Adolf Belka
2026-09-22 17:24 ` [PATCH] libxxhash: Update to version 0.8.4 Adolf Belka
2026-09-22 17:24 ` [PATCH] nfs: Update to version 3.1.1 Adolf Belka
2026-09-22 17:24 ` [PATCH] readline: Update to version 8.3 Patch-6 Adolf Belka
2026-09-22 17:24 ` [PATCH] xfsprogs: Update to version 7.2.0 Adolf Belka
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=20260922172417.3447503-6-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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