Hello community, here is the log from the commit of package xz for openSUSE:Factory checked in at 2020-03-31 17:31:11 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/xz (Old) and /work/SRC/openSUSE:Factory/.xz.new.3160 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "xz" Tue Mar 31 17:31:11 2020 rev:66 rq:788081 version:5.2.5 Changes: -------- --- /work/SRC/openSUSE:Factory/xz/xz.changes 2019-09-26 20:36:05.971365634 +0200 +++ /work/SRC/openSUSE:Factory/.xz.new.3160/xz.changes 2020-03-31 17:31:12.392223987 +0200 @@ -1,0 +2,38 @@ +Wed Mar 18 11:11:48 UTC 2020 - Paolo Stivanin <i...@paolostivanin.com> + +- Update to 5.2.5: + * liblzma: + - Fixed several C99/C11 conformance bugs. Now the code is clean + under gcc/clang -fsanitize=undefined. Some of these changes + might have a negative effect on performance with old GCC + versions or compilers other than GCC and Clang. The configure + option --enable-unsafe-type-punning can be used to (mostly) + restore the old behavior but it shouldn't normally be used. + - Improved API documentation of lzma_properties_decode(). + - Added a very minor encoder speed optimization. + * xz: + - Fixed a crash in "xz -dcfv not_an_xz_file". All four options + were required to trigger it. The crash occurred in the + progress indicator code when xz was in passthru mode where + xz works like "cat". + - Fixed an integer overflow with 32-bit off_t. It could happen + when decompressing a file that has a long run of zero bytes + which xz would try to write as a sparse file. Since the build + system enables large file support by default, off_t is + normally 64-bit even on 32-bit systems. + - Fixes for --flush-timeout: + * Fix semi-busy-waiting. + * Avoid unneeded flushes when no new input has arrived + since the previous flush was completed. + - Added a special case for 32-bit xz: If --memlimit-compress is + used to specify a limit that exceeds 4020 MiB, the limit will + be set to 4020 MiB. The values "0" and "max" aren't affected + by this and neither is decompression. This hack can be + helpful when a 32-bit xz has access to 4 GiB address space + but the specified memlimit exceeds 4 GiB. This can happen + e.g. with some scripts. + - Capsicum sandbox is now enabled by default where available + (FreeBSD >= 10). The sandbox debug messages (xz -vv) were + removed since they seemed to be more annoying than useful. + +------------------------------------------------------------------- Old: ---- xz-5.2.4.tar.gz xz-5.2.4.tar.gz.sig New: ---- xz-5.2.5.tar.gz xz-5.2.5.tar.gz.sig ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ xz.spec ++++++ --- /var/tmp/diff_new_pack.Ll4G4c/_old 2020-03-31 17:31:13.092224397 +0200 +++ /var/tmp/diff_new_pack.Ll4G4c/_new 2020-03-31 17:31:13.092224397 +0200 @@ -1,7 +1,7 @@ # # spec file for package xz # -# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2020 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -19,12 +19,12 @@ # avoid bootstrapping problem %define _binary_payload w9.bzdio Name: xz -Version: 5.2.4 +Version: 5.2.5 Release: 0 Summary: A Program for Compressing Files with the Lempel–Ziv–Markov algorithm License: LGPL-2.1-or-later AND GPL-2.0-or-later AND SUSE-Public-Domain Group: Productivity/Archiving/Compression -Url: http://tukaani.org/xz/ +URL: http://tukaani.org/xz/ Source0: http://tukaani.org/xz/%{name}-%{version}.tar.gz Source1: http://tukaani.org/xz/%{name}-%{version}.tar.gz.sig Source2: baselibs.conf @@ -124,6 +124,7 @@ %if 0%{?lang_package:1} %files lang -f %{name}.lang %defattr(-, root, root) +%{_mandir}/de/man1/*.1%{ext_man} %endif %files ++++++ xz-5.2.4.tar.gz -> xz-5.2.5.tar.gz ++++++ ++++ 42849 lines of diff (skipped)
