Accepting request 354390 from devel:libraries:c_c++

1

OBS-URL: https://build.opensuse.org/request/show/354390
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/pcre2?expand=0&rev=3
This commit is contained in:
Dominique Leuenberger 2016-01-20 08:54:36 +00:00 committed by Git OBS Bridge
parent 814a971bff
commit 86a97fdbae
6 changed files with 41 additions and 5 deletions

View File

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

Binary file not shown.

3
pcre2-10.21.tar.bz2 Normal file
View File

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

BIN
pcre2-10.21.tar.bz2.sig Normal file

Binary file not shown.

View File

@ -1,3 +1,39 @@
-------------------------------------------------------------------
Sun Jan 17 14:30:53 UTC 2016 - jengelh@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.
-------------------------------------------------------------------
Tue Jul 14 08:42:04 UTC 2015 - astieger@suse.com

View File

@ -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