1
0
Fork 0

Merging upstream version 1.20.

Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-21 11:28:50 +01:00
parent 72bcf08df5
commit e24aefbbb2
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
31 changed files with 1242 additions and 685 deletions

53
NEWS
View file

@ -1,17 +1,46 @@
Changes in version 1.19:
Changes in version 1.20:
'--merge' is now able to fix files with thousands of scattered errors
per member by grouping the errors into clusters and then merging the
files as if each cluster were a single error.
Splitting was broken for files larger than 64 KiB because of a bug
introduced in version 1.16.
The option '-a, --trailing-error' now works with '-l, --list' and
'-D, --range-decompress'.
The options "--dump-tdata", "--remove-tdata", and "--strip-tdata" have
been added to ease the management of metadata stored as trailing data:
The output of option '-l, --list' has been simplified to make it easier
to read.
"--dump-tdata" dumps the trailing data (if any) of one or more regular
files to standard output.
In test mode, lziprecover now continues checking the rest of the files
if any input file is a terminal.
"--remove-tdata" removes the trailing data from regular files in place.
Trailing data are now shown both in hexadecimal and as a string of
printable ASCII characters.
"--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 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.