From 48053e8a4550233af46359024538bff90c870ab1 Mon Sep 17 00:00:00 2001 From: Lasse Collin Date: Sun, 22 May 2011 16:42:11 +0300 Subject: [PATCH] Update NEWS for 5.0.3. --- NEWS | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/NEWS b/NEWS index 1e882c24..2986b51b 100644 --- a/NEWS +++ b/NEWS @@ -45,6 +45,38 @@ XZ Utils Release Notes experimental and may change before it gets into a stable release. +5.0.3 (2011-05-21) + + * liblzma fixes: + + - A memory leak was fixed. + + - lzma_stream_buffer_encode() no longer creates an empty .xz + Block if encoding an empty buffer. Such an empty Block with + LZMA2 data would trigger a bug in 5.0.1 and older (see the + first bullet point in 5.0.2 notes). When releasing 5.0.2, + I thought that no encoder creates this kind of files but + I was wrong. + + - Validate function arguments better in a few functions. Most + importantly, specifying an unsupported integrity check to + lzma_stream_buffer_encode() no longer creates a corrupt .xz + file. Probably no application tries to do that, so this + shouldn't be a big problem in practice. + + - Document that lzma_block_buffer_encode(), + lzma_easy_buffer_encode(), lzma_stream_encoder(), and + lzma_stream_buffer_encode() may return LZMA_UNSUPPORTED_CHECK. + + - The return values of the _memusage() functions are now + documented better. + + * Fix command name detection in xzgrep. xzegrep and xzfgrep now + correctly use egrep and fgrep instead of grep. + + * French translation was added. + + 5.0.2 (2011-04-01) * LZMA2 decompressor now correctly accepts LZMA2 streams with no