gzip: Update to 1.9

  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@ipfire.org>
---
 lfs/gzip | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
  

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@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)
>