Hello community, here is the log from the commit of package pcre for openSUSE:Factory checked in at 2018-10-01 09:01:43 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/pcre (Old) and /work/SRC/openSUSE:Factory/.pcre.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "pcre" Mon Oct 1 09:01:43 2018 rev:71 rq:633754 version:8.42 Changes: -------- --- /work/SRC/openSUSE:Factory/pcre/pcre.changes 2018-04-22 14:35:56.712989058 +0200 +++ /work/SRC/openSUSE:Factory/.pcre.new/pcre.changes 2018-10-01 09:01:53.720075903 +0200 @@ -1,0 +2,46 @@ +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. + +------------------------------------------------------------------- Old: ---- pcre-8.41.tar.bz2 pcre-8.41.tar.bz2.sig New: ---- pcre-8.42.tar.bz2 pcre-8.42.tar.bz2.sig ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ pcre.spec ++++++ --- /var/tmp/diff_new_pack.i9o5hy/_old 2018-10-01 09:01:55.236074581 +0200 +++ /var/tmp/diff_new_pack.i9o5hy/_new 2018-10-01 09:01:55.240074578 +0200 @@ -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 ++++++ pcre-8.41.tar.bz2 -> pcre-8.42.tar.bz2 ++++++ ++++ 15573 lines of diff (skipped)