From patchwork Tue Jan 9 04:14:30 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Matthias Fischer X-Patchwork-Id: 1599 Return-Path: Received: from mail01.ipfire.org (unknown [172.28.1.200]) by web02.ipfire.org (Postfix) with ESMTP id B8590600DA for ; Mon, 8 Jan 2018 18:14:36 +0100 (CET) Received: from mail01.ipfire.org (localhost [IPv6:::1]) by mail01.ipfire.org (Postfix) with ESMTP id 4947D1E7B; Mon, 8 Jan 2018 18:14:36 +0100 (CET) Received: from Devel.localdomain (p4FDF0C34.dip0.t-ipconnect.de [79.223.12.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mail01.ipfire.org (Postfix) with ESMTPSA id 3F0D5BAA for ; Mon, 8 Jan 2018 18:14:34 +0100 (CET) From: Matthias Fischer To: development@lists.ipfire.org Subject: [PATCH] gzip: Update to 1.9 Date: Mon, 8 Jan 2018 18:14:30 +0100 Message-Id: <20180108171430.29277-1-matthias.fischer@ipfire.org> X-Mailer: git-send-email 2.15.1 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" Excerpt from 'NEWS': "* 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." Best, Matthias Signed-off-by: Matthias Fischer --- lfs/gzip | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/gzip b/lfs/gzip index 233c6ce40..2318338cf 100644 --- a/lfs/gzip +++ b/lfs/gzip @@ -24,7 +24,7 @@ include Config -VER = 1.8 +VER = 1.9 THISAPP = gzip-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -49,7 +49,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = f7caabb65cddc1a4165b398009bd05b9 +$(DL_FILE)_MD5 = 9492c6ccb2239ff679a5475a7bb543ed install : $(TARGET)