[Lzip-bug] Lunzip 1.10-rc1 released

[Antonio Diaz Diaz]

Lunzip 1.10-rc1 is ready for testing here
http://download.savannah.gnu.org/releases/lzip/lunzip/lunzip-1.10-rc1.tar.lz
http://download.savannah.gnu.org/releases/lzip/lunzip/lunzip-1.10-rc1.tar.gz

The sha256sums are:
3136117d49e54c37adc1384ec7517853f8ba23d8b92384ea5c0f6067b9d29daa 
lunzip-1.10-rc1.tar.lz
ca488c4aa716ea797af1186a7c38c769cd25ecfea7e70027209f94dd12976024 
lunzip-1.10-rc1.tar.gz

Please, test it and report any bugs you find.

Lunzip is a decompressor for lzip files. It is written in C and its 
small size makes it well suited for embedded devices or software 
installers that need to decompress files but do not need compression 
capabilities. Lunzip is fully compatible with lzip-1.4 or newer and is 
able to decompress any lzip file using as little memory as 50 kB.

The lzip file format is designed for data sharing and long-term 
archiving, taking into account both data integrity and decoder availability.

The homepage is at http://www.nongnu.org/lzip/lunzip.html


Changes in this version:

  * The option '--loose-trailing', has been added.

  * The test used by lunzip to discriminate trailing data from a 
corrupt header in multimember or concatenated files has been improved to 
a Hamming distance (HD) of 3, and the 3 bit flips must happen in 
different magic bytes for the test to fail. As a consequence some kinds 
of files no longer can be appended to a lzip file as trailing data 
unless the '--loose-trailing' option is used when decompressing.
Lziprecover can be used to remove conflicting trailing data from a file.

  * The contents of a corrupt or truncated header found in a 
multimember file is now shown, after the error message, in the same 
format as trailing data.

  * The 'bits/byte' ratio has been replaced with the inverse 
compression ratio in the output.

  * The progress of decompression is now shown at verbosity level 2 
(-vv) or higher.

  * Progress of decompression is only shown if stderr is a terminal.

  * A final diagnostic is now shown at verbosity level 1 (-v) or higher 
if any file fails the test when testing multiple files.

  * In case of (de)compressed size mismatch, the stored size is now 
also shown in hexadecimal to ease visual comparison.

  * The dictionary size is now shown at verbosity level 4 (-vvvv) when 
decompressing or testing.


Regards,
Antonio Diaz, lunzip author and maintainer.

--
If you are distributing software in xz format, please consider using 
lzip instead. See http://www.nongnu.org/lzip/lzip_benchmark.html#xz1 and 
http://www.nongnu.org/lzip/xz_inadequate.html