Hello community,
here is the log from the commit of package grep for openSUSE:Factory checked in
at 2016-04-30 23:22:53
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/grep (Old)
and /work/SRC/openSUSE:Factory/.grep.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "grep"
Changes:
--------
--- /work/SRC/openSUSE:Factory/grep/grep.changes 2015-12-03
13:24:58.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.grep.new/grep.changes 2016-04-30
23:22:54.000000000 +0200
@@ -1,0 +2,71 @@
+Fri Apr 22 13:49:18 UTC 2016 - astie...@suse.com
+
+- grep 2.25:
+ * In the C or POSIX locale, grep now treats all bytes as valid
+ characters even if the C runtime library says otherwise.
+ ( Fixes yast2-users and other build failures - boo#966780 )
+ * grep -oz now uses null bytes, not newlines, to terminate output
+ lines.
+ * grep now outputs details more consistently when reporting a
+ write error.
+
+-------------------------------------------------------------------
+Fri Mar 11 09:30:02 UTC 2016 - mplus...@suse.com
+
+- Update to 2.24
+ * grep -z would match strings it should not. To trigger the bug,
+ you'd have to use a regular expression including an anchor
+ (^ or $) and a feature like a range or a backreference, causing
+ grep to forego its DFA matcher and resort to using re_search.
+ With a multibyte locale, that matcher could mistakenly match a
+ string containing a newline. For example, this command:
+ printf 'a\nb\0' | LC_ALL=en_US.utf-8 grep -z '^[a-b]*b'
+ would mistakenly match and print all four input bytes. After
+ the fix, there is no match, as expected.
+ [bug introduced in grep-2.7]
+ * grep -Pz now diagnoses attempts to use patterns containing ^
+ and $, instead of mishandling these patterns. This problem
+ seems to be inherent to the PCRE API; removing this limitation
+ is on PCRE's maint/README wish list. Patterns can continue to
+ match literal ^ and $ by escaping them with \ (now needed even
+ inside [...]). [bug introduced in grep-2.5]
+
+-------------------------------------------------------------------
+Fri Feb 5 08:01:46 UTC 2016 - mplus...@suse.com
+
+- Update to 2.23
+ * Binary files are now less likely to generate diagnostics and
+ more likely to yield text matches. grep now reports "Binary
+ file FOO matches" and suppresses further output instead of
+ outputting a line containing an encoding error; hence grep can
+ now report matching text before a later binary match.
+ Formerly, grep reported FOO to be binary when it found an
+ encoding error in FOO before generating output for FOO, which
+ meant it never reported both matching text and matching binary
+ data; this was less useful for searching text containing
+ encoding errors in non-matching lines. [bug introduced in
+ grep-2.21]
+ * grep -c no longer stops counting when finding binary data.
+ [bug introduced in grep-2.21]
+ * grep no longer outputs encoding errors in unibyte locales. For
+ example, if the byte '\x81' is not a valid character in a
+ unibyte locale, grep treats the byte as binary data. [bug
+ introduced in grep-2.21]
+ * grep -oP is no longer susceptible to an infinite loop when
+ processing invalid UTF8 just before a match. [bug introduced in
+ grep-2.22]
+ * --exclude and related options are now matched against trailing
+ parts of command-line arguments, not against the entire
+ arguments. This partly reverts the --exclude-related change
+ in 2.22. [bug introduced in grep-2.22]
+ * --line-buffer is no longer ineffective when combined with -l.
+ [bug introduced in grep-2.5]
+ * -xw is now equivalent to -x more consistently, with -P and
+ with backrefs. [bug only partially fixed in grep-2.19]
+- Update info handling scriplets
+ * move from postun to preun
+ * add dependeny for preun
+- Refresh partially upstreamed patch
+ * testsuite.patch
+
+-------------------------------------------------------------------
Old:
----
grep-2.22.tar.xz
grep-2.22.tar.xz.sig
New:
----
grep-2.25.tar.xz
grep-2.25.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ grep.spec ++++++
--- /var/tmp/diff_new_pack.jGrtLY/_old 2016-04-30 23:22:55.000000000 +0200
+++ /var/tmp/diff_new_pack.jGrtLY/_new 2016-04-30 23:22:55.000000000 +0200
@@ -1,7 +1,7 @@
#
# spec file for package grep
#
-# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
Name: grep
-Version: 2.22
+Version: 2.25
Release: 0
Summary: Print lines matching a pattern
License: GPL-3.0+
@@ -31,6 +31,7 @@
BuildRequires: pcre-devel
BuildRequires: xz
Requires(pre): %{install_info_prereq}
+Requires(preun): %{install_info_prereq}
Provides: base:%{_bindir}/grep
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%if 0%{?suse_version} < 1120
@@ -84,7 +85,7 @@
%post
%install_info --info-dir=%{_infodir} %{_infodir}/grep.info.gz
-%postun
+%preun
%install_info_delete --info-dir=%{_infodir} %{_infodir}/grep.info.gz
%files -f %{name}.lang
++++++ grep-2.22.tar.xz -> grep-2.25.tar.xz ++++++
++++ 42571 lines of diff (skipped)
++++++ testsuite.patch ++++++
--- /var/tmp/diff_new_pack.jGrtLY/_old 2016-04-30 23:22:56.000000000 +0200
+++ /var/tmp/diff_new_pack.jGrtLY/_new 2016-04-30 23:22:56.000000000 +0200
@@ -17,13 +17,13 @@
tests/mb-non-UTF8-performance | 5 +++++
2 files changed, 10 insertions(+)
-diff --git a/tests/long-pattern-perf b/tests/long-pattern-perf
-index c222c02..2c9d080 100755
---- a/tests/long-pattern-perf
-+++ b/tests/long-pattern-perf
-@@ -20,6 +20,11 @@
-
- fail=0
+Index: grep-2.24/tests/long-pattern-perf
+===================================================================
+--- grep-2.24.orig/tests/long-pattern-perf
++++ grep-2.24/tests/long-pattern-perf
+@@ -25,6 +25,11 @@ fail=0
+ # "expensive", making it less likely to be run by regular users.
+ expensive_
+# This test is susceptible to failure due to differences in
+# system load during the two test runs, so we'll mark it as
@@ -33,22 +33,3 @@
echo x > in || framework_failure_
# We could use seq -s '' (avoiding the tr filter), but I
# suspect some version of seq does not honor that option.
-diff --git a/tests/mb-non-UTF8-performance b/tests/mb-non-UTF8-performance
-index 228361d..9bd5d39 100755
---- a/tests/mb-non-UTF8-performance
-+++ b/tests/mb-non-UTF8-performance
-@@ -22,6 +22,11 @@
-
- fail=0
-
-+# This test is susceptible to failure due to differences in
-+# system load during the two test runs, so we'll mark it as
-+# "expensive", making it less likely to be run by regular users.
-+expensive_
-+
- # Make this large enough so that even on high-end systems
- # it incurs at least 5-10ms of user time.
- yes $(printf '%078d' 0) | head -400000 > in || framework_failure_
---
-2.6.3
-
