summaryrefslogtreecommitdiffstats
path: root/NEWS
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2018-02-13 06:58:53 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2018-02-13 06:59:21 +0000
commit7dd21df678aafaba8614ffe90188712f13b3bfc3 (patch)
treebbfc9eedb166e5e3e154b4ad28f4212bdb239d03 /NEWS
parentReleasing debian version 1.9-4. (diff)
downloadlunzip-7dd21df678aafaba8614ffe90188712f13b3bfc3.tar.xz
lunzip-7dd21df678aafaba8614ffe90188712f13b3bfc3.zip
Merging upstream version 1.10.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS36
1 files changed, 27 insertions, 9 deletions
diff --git a/NEWS b/NEWS
index 57ec920..cd904d7 100644
--- a/NEWS
+++ b/NEWS
@@ -1,14 +1,32 @@
-Changes in version 1.9:
+Changes in version 1.10:
-The option '-l, --list' has been ported from lziprecover.
+The option '--loose-trailing', has been added.
-It is now an error to specify two or more different operations in the
-command line (--decompress, --list or --test).
+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.
-Decompression time has been reduced by 7%.
+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.
-In test mode, lunzip now continues checking the rest of the files if any
-input file is a terminal.
+The 'bits/byte' ratio has been replaced with the inverse compression
+ratio in the output.
-Trailing data are now shown both in hexadecimal and as a string of
-printable ASCII characters.
+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.