|Index||index by Group||index by Distribution||index by Vendor||index by creation date||index by Name||Mirrors||Help||Search|
|Name: grep||Distribution: openSUSE Leap 15.1|
|Version: 3.1||Vendor: openSUSE|
|Release: lp151.3.3||Build date: Tue Apr 23 03:46:05 2019|
|Group: Productivity/Text/Utilities||Build host: obs-arm-6|
|Size: 881142||Source RPM: grep-3.1-lp151.3.3.src.rpm|
|Summary: Print lines matching a pattern|
The grep command searches one or more input files for lines containing a match to a specified pattern. By default, grep prints the matching lines.
* Thu Feb 22 2018 firstname.lastname@example.org - Use %license (boo#1082318) * Mon Jul 03 2017 email@example.com - Update to grep 3.1 * grep '[0-9]' is now just as fast as grep '[[:digit:]]' when run in a multi-byte locale * Context no longer excludes selected lines omitted because of -m * Thu Jun 01 2017 firstname.lastname@example.org - Use https url's - Drop no longer needed explicit pie - Enable profiled build * Sat Feb 11 2017 email@example.com - Update to version 3.0: * grep without -F no longer goes awry when given two or more patterns that contain no special characters other than '\' and also contain a subpattern like '\.' that escapes a character to make it ordinary. * grep no longer fails to build on PCRE versions before 8.20. - Cleanup spec file: * Drop support for old distributions * Create lang subpackage * Use fdupes to replace duplicate files with symlinks * Wed Feb 08 2017 firstname.lastname@example.org - Update to version 2.28: * Improve performance for -E or -G pattern lists that are easily converted to -F format. * Fix performance regression with multiple patterns. * When standard output is /dev/null, grep no longer fails when standard input is a file in the Linux /proc file system, or when standard input is a pipe and standard output is in append mode. * When grep -Fo finds matches of differing length, it could mistakenly print a shorter one. Now it prints a longest one. - Drop upstreamed proc-lseek-glitch.patch * Mon Dec 12 2016 email@example.com - testsuite.patch: remove - proc-lseek-glitch.patch: work around proc lseek glitch * Wed Dec 07 2016 firstname.lastname@example.org - Update to grep 2.27 * grep no longer reports a false match in a multibyte, non-UTF8 locale like zh_CN.gb18030, with a regular expression like ".*7" that just happens to match the 4-byte representation of gb18030's \uC9, the final byte of which is the digit "7". * grep by default now reads all of standard input if it is a pipe, even if this cannot affect grep's output or exit status. * grep no longer mishandles ranges in nontrivial unibyte locales. * grep -P no longer attempts multiline matches. * grep -m0 -L PAT FILE now outputs "FILE". * To output ':' and tab-align the following character C, grep -T no longer outputs tab-backspace-':'-C, an approach that has problems if run inside an Emacs shell window. * grep -T now uses worst-case widths of line numbers and byte offsets instead of guessing widths that might not work with larger files. * grep no longer reads the input in a few more cases when it is easy to see that matching cannot succeed, e.g., 'grep -f /dev/null'. * Fri Oct 28 2016 email@example.com - grep 2.26: * no longer omit output merely because it follows an output line suppressed due to encoding errors * In the Shift_JIS locale, no longer mistakenly match in the middle of a multibyte character * grep can be much faster now when standard output is /dev/null. * grep -F is now typically much faster when many patterns are given, as it now uses the Aho-Corasick algorithm instead of the Commentz-Walter algorithm in that case. * grep -iF is typically much faster in a multibyte locale, if the pattern and its case counterparts contain only single byte characters. * grep with complicated expressions (e.g., back-references) and without -i now uses the regex fastmap for better performance. * In multibyte locales, grep now handles leading "." in patterns more efficiently. * grep now prints a "FILENAME:LINENO: " prefix when diagnosing an invalid regular expression that was read from an '-f'-specified file. * Fri Apr 22 2016 firstname.lastname@example.org - 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 2016 email@example.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 05 2016 firstname.lastname@example.org - 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 * Thu Nov 26 2015 email@example.com - testsuite.patch: also disable long-pattern-perf test * Tue Nov 03 2015 firstname.lastname@example.org - testsuite.patch: disable unreliable test mb-non-UTF8-performance * Mon Nov 02 2015 email@example.com - GNU grep 2.22: * Improve performance for patterns containing very long strings * Output and pattern matching bug fixes - drop add gnulib-perl522.patch, changed upstream - drop grep-F-heap-overrun.patch, included upstream * Mon Jul 06 2015 firstname.lastname@example.org - add gnulib-perl522.patch from gnulib.bugs * Mon Jan 26 2015 email@example.com - grep-F-heap-overrun.patch: fix heap overrun with grep -F (CVE-2015-1345, bsc#914695) * Mon Jan 12 2015 firstname.lastname@example.org - Fix last change * Tue Dec 30 2014 email@example.com - build with PIE enabled * Fri Nov 28 2014 firstname.lastname@example.org - GNU grep 2.21 - Improvements: * performance improved for searching files containing holes, on platforms where lseek's SEEK_DATA flag works efficiently. * performance improved for rejecting data that cannot match even the first part of a nontrivial pattern. * performance improved for very long strings in patterns. * If a file contains data improperly encoded for the current locale, and this is discovered before any of the file's contents are output, grep now treats the file as binary. * -P no longer reports an error and exits when given invalid UTF-8 data. Instead, it considers the data to be non-matching. - Bug fixes: * fix issues in multibyte locales * grep -F -x -o no longer prints an extra newline for each match. * grep in a non-UTF8 multibyte locale could mistakenly match in the middle of a multibyte character when using a '^'-anchored alternate in a pattern, leading it to print non-matching lines. * grep -F Y no longer fails to match in non-UTF8 multibyte locales * grep -E rejected unmatched ')', instead of treating it like '\)'. - Changes in behavior: * The GREP_OPTIONS environment variable is now obsolescent * In locales with multibyte character encodings other than UTF-8, grep -P now reports an error and exits instead of misbehaving. * When searching binary data, grep now may treat non-text bytes as line terminators. This can boost performance significantly. * grep -z no longer automatically treats the byte '\200' as binary data.
/bin/egrep /bin/fgrep /bin/grep /usr/bin/egrep /usr/bin/fgrep /usr/bin/grep /usr/share/doc/packages/grep /usr/share/doc/packages/grep/AUTHORS /usr/share/doc/packages/grep/ChangeLog /usr/share/doc/packages/grep/ChangeLog-2009 /usr/share/doc/packages/grep/NEWS /usr/share/doc/packages/grep/README /usr/share/doc/packages/grep/THANKS /usr/share/doc/packages/grep/TODO /usr/share/info/grep.info.gz /usr/share/licenses/grep /usr/share/licenses/grep/COPYING /usr/share/man/man1/egrep.1.gz /usr/share/man/man1/fgrep.1.gz /usr/share/man/man1/grep.1.gz
Generated by rpm2html 1.8.1
Fabrice Bellet, Sun Nov 10 11:29:41 2019