GNU bug report logs - #31065
Version 2??

Previous Next

Package: gzip;

Reported by: - - <computing <at> windcheetah.org.uk>

Date: Wed, 4 Apr 2018 21:57:01 UTC

Severity: normal

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 31065 <at> debbugs.gnu.org (full text, mbox):

From: Mark Adler <madler <at> alumni.caltech.edu>
To: computing <at> windcheetah.org.uk
Cc: 31065 <at> debbugs.gnu.org
Subject: Re: bug#31065: Version 2??
Date: Wed, 4 Apr 2018 16:01:00 -0700
Jean-loup has not worked on gzip for many years, but I will leave it to the gzip maintainers here to answer to their future intentions.

However pigz has that ability now with the --independent option, where the block size defaults to 128K, and can be changed with the --blocksize option. See http://zlib.net/pigz/

> On Apr 4, 2018, at 2:10 PM, - - <computing <at> windcheetah.org.uk> wrote:
> 
>   Hi, some time ago Jean-loup, said on [1]http://www.gzip.org/recover.txt
>   that
>   "As you can see, all this is not a trivial task, so you should attempt
>   it only if your data is very valuable. gzip 2.0 will have a new
>   blocksize option, allowing to recover easily all undamaged blocks after
>   the damaged portion."
>   I'm using gzip 1.9 from the PCLinuxOS.
>   Can you please let me know:
>   1 Is it still the plan to get this into 2.0?
>   2 If you are, when do you think 2.0 will be out??
>   Thanks loads
>   Martin
> 
> References
> 
>   1. http://www.gzip.org/recover.txt





This bug report was last modified 7 years and 73 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.