[Lzip-bug] Lziprecover 1.20 released

[Antonio Diaz Diaz]

I am pleased to announce the release of lziprecover 1.20.

Lziprecover is a data recovery tool and decompressor for files in the 
lzip compressed data format (.lz). Lziprecover is able to repair 
slightly damaged files, produce a correct file by merging the good parts 
of two or more damaged copies, extract data from damaged files, 
decompress files and test integrity of files.

Lziprecover provides random access to the data in multimember files; it 
only decompresses the members containing the desired data.

Lziprecover is not a replacement for regular backups, but a last line of 
defense for the case where the backups are also damaged.

Lziprecover is able to recover or decompress files produced by any of 
the compressors in the lzip family; lzip, plzip, minilzip/lzlib, clzip 
and pdlzip.

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

A nice feature of the lzip format is that a corrupt byte is easier to 
repair the nearer it is from the beginning of the file. Therefore, with 
the help of lziprecover, losing an entire archive just because of a 
corrupt byte near the beginning is a thing of the past.

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

The sources can be downloaded from 
http://download.savannah.gnu.org/releases/lzip/lziprecover/

The sha256sums are:
c4673d998f9302f8d1533b21393fd6457989d7c9f4fb62eb9d5b0a395568d3ac 
lziprecover-1.20.tar.lz
ffd79a038c9910c139a9339c1d9689320c927733c0a4998173a16daf7aabf63a 
lziprecover-1.20.tar.gz

This release is also GPG signed. You can download the signature by 
appending '.sig' to the URL. If the 'gpg --verify' command fails because 
you don't have the required public key, then run this command to import it:

  gpg --keyserver keys.gnupg.net --recv-keys 8FE99503132D7742

Key fingerprint = 1D41 C14B 272A 2219 A739  FA4F 8FE9 9503 132D 7742


Changes in version 1.20:

  * Splitting was broken for files larger than 64 KiB because of a bug 
introduced in version 1.16. (Thanks to Hampa Hug for reporting this).

  * The options "--dump-tdata", "--remove-tdata", and "--strip-tdata" 
have been added to ease the management of metadata stored as trailing data:

  "--dump-tdata" dumps the trailing data (if any) of one or more 
regular files to standard output.

  "--remove-tdata" removes the trailing data from regular files in place.

  "--strip-tdata" copies one or more regular files to standard output, 
stripping the trailing data (if any) from each file.

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

  * The test used by lziprecover 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 are 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.


Please send bug reports and suggestions to address@hidden


Regards,
Antonio Diaz, lziprecover 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