Changelog for grep-debugsource-2.16-7.3.x86_64.rpm :

* Wed Sep 16 2015 schwabAATTsuse.de- pcre-utf8.patch: Avoid undefined behaviour with -P and non-utf-8 data (bsc#920386)
* Sun Jan 05 2014 andreas.stiegerAATTgmx.de- update to 2.16
* Fix gnulib-provided maint.mk to report correct version number
* The fix to make \\s and \\S work with multi-byte white space broke the use of each shortcut whenever followed by a repetition operator. For example, \\s
*, \\s+, \\s? and \\s{3} would all malfunction in a multi-byte locale.
* The fix to make grep -P work better with UTF-8 made it possible for grep to evoke a larger set of PCRE errors, some of which could trigger an abort. E.g., this would abort: printf \'\\x82\'|LC_ALL=en_US.UTF-8 grep -P y Now grep handles arbitrary PCRE errors
* Handle very long lines (2GiB and longer) on systems with a deficient read system call.- removed patches:
* grep-gnulib-ppc64le.patch, upstream source removed
* Mon Dec 23 2013 cooloAATTsuse.com- don\'t drag texlive into bootstrap cycle - makeinfo is enough
* Fri Dec 20 2013 uweigandAATTde.ibm.com- grep-gnulib-ppc64le.patch: Fix imported gnulib long double math tests for little-endian PowerPC.
* Wed Dec 11 2013 andreas.stiegerAATTgmx.de- Update to 2.15: Bug fixes:
* grep\'s \\s and \\S failed to work with multi-byte white space characters.
* grep -i would segfault on systems using UTF-16-based wchar_t when converting an input string containing certain 4-byte UTF-8 sequences to lower case.
* grep -E would segfault when given a regexp like \'([^.]
*[M]){1,2}\' for any multibyte character M.
* grep -F would get stuck in an infinite loop when given a search string that is an invalid byte sequence in the current locale and that matches the bytes of the input twice on a line. Now grep fails with exit status 1.
* grep -P could misbehave. New features:
* grep -P can now use a just-in-time compiler to greatly speed up matches, This feature is transparent to the user; no flag is required to enable it. It is only available if the corresponding support in the PCRE library is detected when grep is compiled.- require xz for SLE- require texinfo for makeinfo- don\'t autoreconf- remove the added german translations, upstream is up-to-date
* Wed Mar 27 2013 mmeisterAATTsuse.com- Added url as source. Please see http://en.opensuse.org/SourceUrls
* Fri Aug 24 2012 pthAATTsuse.de- Update to 2.14: Bug fixes:
* grep -i \'^$\' could exit 0 (i.e., report a match) in a multi-byte locale, even though there was no match, and the command generated no output. E.g., seq 2 | LC_ALL=en_US.utf8 grep -il \'^$\' would mistakenly print \"(standard input)\". Related, seq 9 | LC_ALL=en_US.utf8 grep -in \'^$\' would print \"2:4:6:8:10:12:14:16\" and exit 0. Now it prints nothing and exits with status of 1. [bug introduced in grep-2.6]
* \'grep\' no longer falsely reports text files as being binary on file systems that compress contents or that store tiny contents in metadata.- Add current German message catalog from the translation project.
* Thu Jul 05 2012 jsmeixAATTsuse.de- Update to 2.13: It\'s moderately important to upgrade from grep-2.6 or newer, since a Turkish I-with-dot (U+0130) on a matched/printed line makes \"grep -i\" (in nearly any UTF-8 locale) emit corrupt output. Bug fixes:
* grep -i, in a multi-byte locale, when matching a line containing a character like the UTF-8 Turkish I-with-dot (U+0130) (whose lower-case representation occupies fewer bytes), would print an incomplete output line. Similarly, with a matched line containing a character (e.g., the Latin capital I in a Turkish UTF-8 locale), where the lower-case representation occupies more bytes, grep could print garbage. [bug introduced in grep-2.6]
* --include and --exclude can again be combined, and again apply to the command line, e.g., \"grep --include=\'
*.[ch]\' - -exclude=\'system.h\' PATTERN
*\" again reads all
*.c and
*.h files except for system.h. [bug introduced in grep-2.6] New features:
* \'grep\' without -z now treats a sparse file as binary, if it can easily determine that the file is sparse. Dropped features:
* Bootstrapping with Makefile.boot has been broken since grep 2.6, and was removed.
* Mon May 21 2012 tabrahamAATTnovell.com- Update to 2.12:
* \"echp P|grep --devices=skip P\" once again prints P, as it did in 2.10 [bug introduced in grep-2.11]
* grep no longer segfaults with -r --exclude-dir and no file operand. I.e., \":|grep -r --exclude-dir=D PAT\" would segfault. [bug introduced in grep-2.11]
* Recursive grep now uses fts for directory traversal, so it can handle much-larger directories without reporting things like \"Filename too long\", and it can run much faster when dealing with large directory hierarchies. [bug present since the beginning]
* grep -E \'a{1000000000}\' now reports an overflow error rather than silently acting like grep -E \'a\\{1000000000}\'.
* The -R option now has a long-option alias --dereference-recursive.
* The -r (--recursive) option now follows only command-line symlinks. Also, by default -r now reads a device only if it is named on the command line; this can be overridden with --devices. - R acts as before, so use -R if you prefer the old behavior of following all symlinks and defaulting to reading all devices.
* Thu Apr 19 2012 meissnerAATTsuse.de- use -mlong-double-64 on ppc
*
* Tue Mar 13 2012 tabrahamAATTnovell.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
* Sat Feb 04 2012 rschweikertAATTsuse.com- keep executables in /usr tree (UsrMerge project)
* Fri Dec 02 2011 cfarrellAATTsuse.com- license update: GPL-3.0+ There are no GPL-3.0 files in the package.
* Thu Dec 01 2011 cooloAATTsuse.com- add automake as buildrequire to avoid implicit dependency
* Sat Oct 29 2011 meissnerAATTsuse.com- disable the long double checks on ppc
* as they dont meet the preconditions in their double vs long double usage.
* Tue Sep 27 2011 dmuellerAATTsuse.de- fix testsuite to build properly against locally built grep
* Wed Aug 10 2011 crrodriguezAATTopensuse.org- Upgrade to version 2.9
* grep no longer clobbers heap for an ERE like \'(^| )
*( |$)\'\' )\'
* grep -P no longer aborts when PCRE\'s backtracking limit is exceeded
* grep\'s interpretation of range expression is now more consistent
* Fri Sep 24 2010 jsmeixAATTsuse.de- Replaced configure typo \'--without-included-rege\' in grep.spec (only in case of suse_version < 1120) with \'--without-included-regex\' (which is the default on systems with recent-enough version of the GNU C Library).
* Thu Sep 23 2010 jsmeixAATTsuse.de- Version upgrade to grep-2.7 with new behavior: grep now diagnoses (and fails with exit status 2) commonly mistyped regular expression like [:space:], [:digit:], etc. Before, those were silently interpreted as [ac:eps] and [dgit:] respectively. This new behavior is disabled when the POSIXLY_CORRECT environment variable is set. Regular expressions including back references are now significantly faster in multi-byte locales. Regular expressions including \".\" can now be significantly faster in UTF-8 locales (though not in other multi-byte locales). Several other minor bugs were fixed. For details see the NEWS file.- Adapted RPM description text to match the \"Introduction to grep\" at http://www.gnu.org/software/grep/ and removed the outdated Authors section, see the AUTHORS file for the right authors.- Enhanced RPM spec file so that it builds and can be provided even for older openSUSE and SLES versions.
* Thu Jul 22 2010 jsmeixAATTsuse.de- Forwarded the below \"upgrade to grep-2.6.3\" to openSUSE:Factory. This is also a reset to full compliance with upstream. All our own patches and \"speedups\" were dropped in the below \"upgrade to grep-2.6.3\" because they had bad side effects like bnc#618455 (SLES11-SP1) and bug#616037 (SLES9-SP4) which do not happen with an upstream compliant grep (regardless of an old version 2.5.1 or the new 2.6.3).- On Fri Apr 9 16:43:45 CEST 2010 duweAATTsuse.de did a version upgrade to grep-2.6.3, which brings among various compile fixes vast improvements for UTF-8 / multibyte handling. Fixes bnc#255977 (SLES10-SP2) and bnc#415228 (SLES9-SP3).
* Mon Jun 28 2010 jengelhAATTmedozas.de- use %_smp_mflags
* Thu Jun 11 2009 cooloAATTnovell.com- rediff to avoid fuzz- fix build with glibc 2.10
* Thu Jun 04 2009 crrodriguezAATTsuse.de- link pcre library dynamically