Accepting request 633007 from home:AndreasStieger:branches:Base:System

pcre 8.42

OBS-URL: https://build.opensuse.org/request/show/633007
OBS-URL: https://build.opensuse.org/package/show/Base:System/pcre?expand=0&rev=89

pcre-8.41.tar.bz2

@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e62c7eac5ae7c0e7286db61ff82912e1c0b7a0c13706616e94a7dd729321b530
-size 1561874

pcre-8.42.tar.bz2

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2cd04b7c887808be030254e8d77de11d3fe9d4505c39d4b15d2664ffe8bf9301
+size 1570171

pcre.changes

@@ -1,3 +1,49 @@
+-------------------------------------------------------------------
+Tue Sep  4 11:46:19 UTC 2018 - astieger@suse.com
+
+- pcre 8.42:
+  * Fix outdated real_pcre definitions in pcre.h.in
+  * pcregrep was truncating components of file names to 128
+    characters when processing files with the -r option, and also
+    truncating path names to 512 characters. There is now a check on
+    the absolute length of full path file names, which may be up to
+    2047 characters long
+  * Using pcre_dfa_exec(), in UTF mode when UCP support was not
+    defined, there was the possibility of a false positive match when
+    caselessly matching a "not this character" item such as
+    [^\x{1234}] (with a code point greater than 127) because the
+    "other case" variable was not being initialized
+  * Although pcre_jit_exec checks whether the pattern is compiled
+    in a given mode, it was also expected that at least one mode is
+    available. This is fixed and pcre_jit_exec returns with
+    PCRE_ERROR_JIT_BADOPTION when the pattern is not optimized by JIT
+    at all.
+  * The line number and related variables such as match counts in
+    pcregrep were all int variables, causing overflow when files with
+    more than 2147483647 lines were processed (assuming 32-bit ints).
+    They have all been changed to unsigned long ints.
+  * If a backreference with a minimum repeat count of zero was first in
+    a pattern, apart from assertions, an incorrect first matching
+    character could be recorded. For example, for the pattern
+    /(?=(a))\1?b/, "b" was incorrectly set as the first character of
+    a match.
+  * Fix out-of-bounds read for partial matching of /./ against an
+    empty string when the newline type is CRLF.
+  * When matching using the the REG_STARTEND feature of the POSIX
+    API with a non-zero starting offset, unset capturing groups
+    with lower numbers than a group that did capture something were
+    not being correctly returned as "unset" (that is, with offset
+    values of -1).
+  * Matching the pattern /(*UTF)\C[^\v]+\x80/ against an 8-bit
+    string containing multi-code-unit characters caused bad
+    behaviour and possibly a crash. This issue was fixed for other
+    kinds of repeat in release 8.37 by change 38, but repeating
+    character classes were overlooked.
+  * A small fix to pcregrep to avoid compiler warnings for
+    -Wformat-overflow=2.
+  * Added --enable-jit=auto support to configure.ac.
+  * Fix misleading error message in configure.ac.
+
 -------------------------------------------------------------------
 Sun Apr 15 00:59:20 UTC 2018 - bwiedemann@suse.com
 

pcre.spec

@@ -17,7 +17,7 @@
 
 
 Name:           pcre
-Version:        8.41
+Version:        8.42
 Release:        0
 Summary:        A library for Perl-compatible regular expressions
 License:        BSD-3-Clause