Hello community, here is the log from the commit of package grep for openSUSE:Factory checked in at 2012-03-16 13:15:41 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/grep (Old) and /work/SRC/openSUSE:Factory/.grep.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "grep", Maintainer is "jsm...@suse.com" Changes: -------- --- /work/SRC/openSUSE:Factory/grep/grep.changes 2012-02-07 14:45:48.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.grep.new/grep.changes 2012-03-16 13:15:43.000000000 +0100 @@ -1,0 +2,72 @@ +Tue Mar 13 18:18:23 UTC 2012 - tabra...@novell.com + +- Update to 2.11: + * grep no longer dumps core on lines whose lengths do not fit in + 'int'. (e.g., lines longer than 2 GiB on a typical 64-bit host). + Instead, grep either works as expected, or reports an error. + An error can occur if not enough main memory is available, or if + the GNU C library's regular expression functions cannot handle + such long lines. [bug present since "the beginning"] + * The -m, -A, -B, and -C options no longer mishandle context line + counts that do not fit in 'int'. Also, grep -c's counts are now + limited by the type 'intmax_t' (typically less than 2**63) rather + than 'int' (typically less than 2**31). + * grep no longer silently suppresses errors when reading a directory + as if it were a text file. For example, "grep x ." now reports a + read error on most systems; formerly, it ignored the error. + [bug introduced in grep-2.5] + * grep now exits with status 2 if a directory loop is found, instead + of possibly exiting with status 0 or 1. [bug introduced in + grep-2.3] + * The -s option now suppresses certain input error diagnostics that + it formerly failed to suppress. These include errors when closing + the input, when lseeking the input, and when the input is also the + output. [bug introduced in grep-2.4] + * On POSIX systems, commands like "grep PAT < FILE >> FILE" now report + an error instead of looping. [bug present since "the beginning"] + * The --include, --exclude, and --exclude-dir options now handle + command-line arguments more consistently. --include and --exclude + apply only to non-directories and --exclude-dir applies only to + directories. "-" (standard input) is never excluded, since it is + not a file name. [bug introduced in grep-2.5] + * grep no longer rejects "grep -qr . > out", i.e., when run with -q + and an input file is the same as the output file, since with -q + grep generates no output, so there is no risk of infinite loop or + of an output-affecting race condition. Thus, the use of the + following options also disables the input-equals-output failure: + --max-count=N (-m) (for N >= 2) + --files-with-matches (-l) + --files-without-match (-L) + [bug introduced in grep-2.10] + * grep no longer emits an error message and quits on MS-Windows when + invoked with the -r option. + * grep no longer misinterprets some alternations involving anchors + (^, $, \< \> \B, \b). For example, grep -E "(^|\B)a" no + longer reports a match for the string "x a". [bug present since + "the beginning"] + * If no file operand is given, and a command-line -r or equivalent + option is given, grep now searches the working directory. Formerly + grep ignored the -r and searched standard input nonrecursively. + An -r found in GREP_OPTIONS does not have this new effect. + * grep now supports color highlighting of matches on MS-Windows. + * Use of the --mmap option now elicits a warning. It has been a no-op + since March of 2010. + * grep no longer diagnoses write errors repeatedly; it exits after + diagnosing the first write error. This is better behavior when + writing to a dangling pipe. + * Syntax errors in GREP_COLORS are now ignored, instead of sometimes + eliciting warnings. This is more consistent with programs that + (e.g.) ignore errors in termcap entries. + +- changes from 2.10: + * grep no longer mishandles high-bit-set pattern bytes on systems + where "char" is a signed type. [bug appears to affect only + MS-Windows] + * On POSIX systems, grep now rejects a command like + "grep -r pattern . > out", in which the output file is also one + of the inputs, because it can result in an "infinite" disk-filling + loop. [bug present since "the beginning"] + +- removed fix-testsuite.diff obsoleted by this release + +------------------------------------------------------------------- Old: ---- fix-testsuite.diff grep-2.9.tar.bz2 New: ---- grep-2.11.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ grep.spec ++++++ --- /var/tmp/diff_new_pack.3YJ71n/_old 2012-03-16 13:15:45.000000000 +0100 +++ /var/tmp/diff_new_pack.3YJ71n/_new 2012-03-16 13:15:45.000000000 +0100 @@ -15,6 +15,8 @@ # Please submit bugfixes or comments via http://bugs.opensuse.org/ # + + Name: grep BuildRequires: automake BuildRequires: pcre-devel @@ -24,14 +26,13 @@ Url: http://www.gnu.org/software/grep/ Provides: base:/usr/bin/grep PreReq: %{install_info_prereq} -Version: 2.9 +Version: 2.11 Release: 0 Summary: Print lines matching a pattern License: GPL-3.0+ Group: Productivity/Text/Utilities Source: grep-%{version}.tar.bz2 -Patch0: fix-testsuite.diff -Patch1: grep-ppc-fix.patch +Patch0: grep-ppc-fix.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build %description @@ -44,11 +45,10 @@ %if 0%{?suse_version} < 1120 echo "ac_cv_search_pcre_compile=\${ac_cv_search_pcre_compile=%{_libdir}/libpcre.a}" >config.cache %endif -%patch0 # If you platform Long Double and Double to not match as expected %ifarch ppc ppc64 -%patch1 -p1 +%patch0 -p1 %endif %build ++++++ grep-2.9.tar.bz2 -> grep-2.11.tar.bz2 ++++++ ++++ 95834 lines of diff (skipped) -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
