public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] gzip: Update to 1.9
Date: Tue, 09 Jan 2018 14:21:16 +0000	[thread overview]
Message-ID: <1515507676.3685.101.camel@ipfire.org> (raw)
In-Reply-To: <20180108171430.29277-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]

Thanks. Merged.

On Mon, 2018-01-08 at 18:14 +0100, Matthias Fischer wrote:
> 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 <matthias.fischer(a)ipfire.org>
> ---
>  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)
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-01-09 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 17:14 Matthias Fischer
2018-01-09 14:21 ` Michael Tremer [this message]

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=1515507676.3685.101.camel@ipfire.org \
    --to=michael.tremer@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