Hello community,

here is the log from the commit of package pcre2 for openSUSE:Factory checked 
in at 2016-01-20 09:54:36
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/pcre2 (Old)
 and      /work/SRC/openSUSE:Factory/.pcre2.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "pcre2"

Changes:
--------
--- /work/SRC/openSUSE:Factory/pcre2/pcre2.changes      2015-08-01 
11:34:05.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.pcre2.new/pcre2.changes 2016-01-20 
09:54:45.000000000 +0100
@@ -1,0 +2,36 @@
+Sun Jan 17 14:30:53 UTC 2016 - jeng...@inai.de
+
+- Update to new upstream release 10.21
+* Improve JIT matching speed of patterns starting with + or *.
+* Use memchr() to find the first character in an unanchored match
+  in 8-bit mode in the interpreter. This gives a significant speed
+  improvement.
+* 10.20 broke the handling of [[:>:]] and [[:<:]] in that
+  processing them could involve a buffer overflow if the
+  following character was an opening parenthesis.
+* 10.20 also introduced a bug in processing this pattern:
+  /((?x)(*:0))#(?'/, which was fixed.
+* A callout with a string argument containing an opening square
+  bracket, for example /(?C$[$)(?<]/, was incorrectly processed and
+  could provoke a buffer overflow.
+* A possessively repeated conditional group that could match an empty
+  string, for example, /(?(R))*+/, was incorrectly compiled.
+* The Unicode tables have been updated to Unicode 8.0.0.
+* An empty comment (?#) in a pattern was incorrectly processed and
+  could provoke a buffer overflow.
+* Fix infinite recursion in the JIT compiler when certain patterns
+  /such as (?:|a|){100}x/ are analysed.
+* Some patterns with character classes involving [: and \\ were
+  incorrectly compiled and could cause reading from uninitialized
+  memory or an incorrect error diagnosis. Examples are:
+  /[[:\\](?<[::]/ and /[[:\\](?'abc')[a:].
+* A missing closing parenthesis for a callout with a string argument
+  was not being diagnosed, possibly leading to a buffer overflow.
+* If (?R was followed by - or + incorrect behaviour happened instead
+  of a diagnostic.
+* Fixed an issue when \p{Any} inside an xclass did not read the current
+  character.
+* About 80 more fixes, which you can read about in the ChangeLog
+  shipped with the libpcre2-8-0 package.
+
+-------------------------------------------------------------------

Old:
----
  pcre2-10.20.tar.bz2
  pcre2-10.20.tar.bz2.sig

New:
----
  pcre2-10.21.tar.bz2
  pcre2-10.21.tar.bz2.sig

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ pcre2.spec ++++++
--- /var/tmp/diff_new_pack.i5kB2D/_old  2016-01-20 09:54:46.000000000 +0100
+++ /var/tmp/diff_new_pack.i5kB2D/_new  2016-01-20 09:54:46.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package pcre2
 #
-# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
 
 
 Name:           pcre2
-Version:        10.20
+Version:        10.21
 Release:        0
 Summary:        A library for Perl-compatible regular expressions
 License:        BSD-3-Clause

++++++ pcre2-10.20.tar.bz2 -> pcre2-10.21.tar.bz2 ++++++
++++ 76481 lines of diff (skipped)


Reply via email to