Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

pcre-devel-8.42-3.1 RPM for ppc64

From OpenSuSE Ports Tumbleweed for ppc64

Name: pcre-devel Distribution: openSUSE Tumbleweed
Version: 8.42 Vendor: openSUSE
Release: 3.1 Build date: Thu Sep 5 12:10:08 2019
Group: Development/Libraries/C and C++ Build host: obs-power8-02
Size: 270559 Source RPM: pcre-8.42-3.1.src.rpm
Packager: http://bugs.opensuse.org
Url: http://www.pcre.org/
Summary: A library for Perl-compatible regular expressions
The PCRE library is a set of functions that implement regular
expression pattern matching using the same syntax and semantics
as Perl 5.

Provides

Requires

License

BSD-3-Clause

Changelog

* Fri Aug 02 2019 Martin Liška <mliska@suse.cz>
  - Use FAT LTO objects in order to provide proper static library.
* Thu Oct 25 2018 lauffer@ph-freiburg.de
  - pcreposix patch taken from debian. Solves cyrus-imapd issue #1731, too.
    pcre-8.42-pcreposix.patch
* Tue Sep 04 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 2018 bwiedemann@suse.com
  - Do not run profiling 'check' in parallel
    to make package build reproducible (boo#1040589)
* Thu Feb 22 2018 fvogt@suse.com
  - Use %license (boo#1082318)
* Wed Nov 01 2017 kstreitova@suse.com
  - add pcre-8.41-stack_frame_size_detection.patch to fix pcre stack
    frame size detection because modern compilers broke it by cloning
    and inlining pcre match() function [bsc#1058722]
* Tue Sep 12 2017 matz@suse.com
  - RunTest needs much stack, on s390x more than the default
    8 MB.  [bnc#1046102]
* Tue Jul 25 2017 astieger@suse.com
  - pcre 8.41:
    * If pcregrep in multiline mode with --only-matching matched
      several lines, it restarted scanning at the next line instead
      of moving on to the end of the matched string, which can be
      several lines after the start.
    * Fix a missing else in the JIT compiler reported by 'idaifish'.
      CVE-2017-6004 bsc#1025709
    * A (?# style comment is now ignored between a basic quantifier
      and a following '+' or '?' (example: /X+(?#comment)?Y/.
    * Avoid use of a potentially overflowing buffer in pcregrep
    * Fix issues reported by fuzzers in pcretest:
    - Check for values < 256 when calling isprint() in pcretest.
    - Give an error for too big a number after \O.
    * In the 32-bit library in non-UTF mode, an attempt to find a
      Unicode property for a character with a code point greater than
      0x10ffff (the Unicode maximum) caused a crash.
      CVE-2017-7186 bsc#1030066, CVE-2017-7244 bsc#1030807
    * The alternative matching function, pcre_dfa_exec() misbehaved
      if it encountered a character class with a possessive repeat,
      for example [a-f]{3}+.
    * When pcretest called pcre_copy_substring() in 32-bit mode, it
      set the buffer length incorrectly, which could result in buffer
      overflow. CVE-2017-7245 bsc#1030805, CVE-2017-7246 bsc#1030803
* Fri Jun 02 2017 mpluskal@suse.com
  - Enable jit on aarch64
  - Enable profiled building
* Thu Feb 09 2017 astieger@suse.com
  - pcre 8.40:
    * Using -o with -M in pcregrep could cause unnecessary repeated
      output when the match extended over a line boundary.
    * Fix register overwite in JIT when SSE2 acceleration is enabled.
    * Ignore "show all captures" (/=) for DFA matching.
    * Fix JIT unaligned accesses on x86
    * In any wide-character mode (8-bit UTF or any 16-bit or 32-bit
      mode), without PCRE_UCP set, a negative character type such as
      \D in a positive class should cause all characters greater than
      255 to match, whatever else is in the class. There was a bug
      that caused this not to happen if a Unicode property item was
      added to such a class, for example [\D\P{Nd}] or [\W\pL].
    * When pcretest was outputing information from a callout, the
      caret indicator for the current position in the subject line
      was incorrect if it was after an escape sequence for a
      character whose code point was greater than \x{ff}.
    * A pattern such as (?<RA>abc)(?(R)xyz) was incorrectly compiled
      such that the conditional was interpreted as a reference to
      capturing group 1 instead of a test for recursion. Any group
      whose name began with R was misinterpreted in this way. (The
      reference interpretation should only happen if the group's name
      is precisely "R".)
    * A number of bugs have been mended relating to match start-up
      optimizations when the first thing in a pattern is a positive
      lookahead. These all applied only when PCRE_NO_START_OPTIMIZE
      was *not* set:
      + A pattern such as (?=.*X)X$ was incorrectly optimized as if
      it needed both an initial 'X' and a following 'X'.
      + Some patterns starting with an assertion that started with
      .* were incorrectly optimized as having to match at the start
      of the subject or after a newline. There are cases where this
      is not true, for example, (?=.*[A-Z])(?=.{8,16})(?!.*[\s])
      matches after the start in lines that start with spaces.
      Starting .* in an assertion is no longer taken as an
      indication of matching at the start (or after a newline).
* Tue Feb 07 2017 dimstar@opensuse.org
  - Explicitly package %{_docdir}/%{name} to fix build with RPM 4.13.
* Mon Aug 01 2016 astieger@suse.com
  - record minor vulnerabilities fixed in 8.39
* Wed Jun 15 2016 mpluskal@suse.com
  - Update to version 8.39:
    * Some appropriate PCRE2 JIT improvements have been retro-fitted
      to PCRE1.
    * CVE-2016-3191: workspace overflow for (*ACCEPT) with deeply
      nested parentheses (boo#971741)
    * CVE-2016-1283: Heap buffer overflow DoS (boo#960837)
    * Apart from that, this is another bug-fix release.
* Thu Nov 26 2015 astieger@suse.com
  - pcre 8.38:
    * CVE-2015-3217: Call Stack Overflow Vulnerability in match()
      bsc#933878
    * Other fixes to assertions, crashes, buffer overflows and
      performance issues found by fuzzer, affecting applications
      accepting regular expression from untrusted sources
* Thu Apr 30 2015 astieger@suse.com
  - pcre 8.37:
    * CVE-2015-2325: Patterns with certain groups specifying a zero
      minimum quantifier caused incorrect code to be compiled,
      leading to an incorrect memory read. [boo#924960]
    * CVE-2015-2326: Specific patterns containing a forward reference
      with subroutine calls caused incorrect code to be compiled
      [boo#924961]
    * CVE-2014-8964: If an assertion condition was quantified with a
      minimum of zero, SIGSEGV or other misbehaviour could occur.
      [boo#906574]
    * further bug fixes as listed in ChangeLog
* Mon Mar 09 2015 p.drouand@gmail.com
  - Update to version 3.16
    * This is primarily a bug-fix release.
    * The Unicode data tables have been updated to Unicode 7.0.0.
  - Remove pcre-commit1472.patch; fixed on upstream release
  - Remove obsolete "Obsoletes" tag

Files

/usr/bin/pcre-config
/usr/include/pcre.h
/usr/include/pcre_scanner.h
/usr/include/pcre_stringpiece.h
/usr/include/pcrecpp.h
/usr/include/pcrecpparg.h
/usr/include/pcreposix.h
/usr/lib64/libpcre.so
/usr/lib64/libpcre16.so
/usr/lib64/libpcrecpp.so
/usr/lib64/libpcreposix.so
/usr/lib64/pkgconfig/libpcre.pc
/usr/lib64/pkgconfig/libpcre16.pc
/usr/lib64/pkgconfig/libpcrecpp.pc
/usr/lib64/pkgconfig/libpcreposix.pc
/usr/share/man/man1/pcre-config.1.gz
/usr/share/man/man3/pcre.3.gz
/usr/share/man/man3/pcre16.3.gz
/usr/share/man/man3/pcre16_assign_jit_stack.3.gz
/usr/share/man/man3/pcre16_compile.3.gz
/usr/share/man/man3/pcre16_compile2.3.gz
/usr/share/man/man3/pcre16_config.3.gz
/usr/share/man/man3/pcre16_copy_named_substring.3.gz
/usr/share/man/man3/pcre16_copy_substring.3.gz
/usr/share/man/man3/pcre16_dfa_exec.3.gz
/usr/share/man/man3/pcre16_exec.3.gz
/usr/share/man/man3/pcre16_free_study.3.gz
/usr/share/man/man3/pcre16_free_substring.3.gz
/usr/share/man/man3/pcre16_free_substring_list.3.gz
/usr/share/man/man3/pcre16_fullinfo.3.gz
/usr/share/man/man3/pcre16_get_named_substring.3.gz
/usr/share/man/man3/pcre16_get_stringnumber.3.gz
/usr/share/man/man3/pcre16_get_stringtable_entries.3.gz
/usr/share/man/man3/pcre16_get_substring.3.gz
/usr/share/man/man3/pcre16_get_substring_list.3.gz
/usr/share/man/man3/pcre16_jit_exec.3.gz
/usr/share/man/man3/pcre16_jit_stack_alloc.3.gz
/usr/share/man/man3/pcre16_jit_stack_free.3.gz
/usr/share/man/man3/pcre16_maketables.3.gz
/usr/share/man/man3/pcre16_pattern_to_host_byte_order.3.gz
/usr/share/man/man3/pcre16_refcount.3.gz
/usr/share/man/man3/pcre16_study.3.gz
/usr/share/man/man3/pcre16_utf16_to_host_byte_order.3.gz
/usr/share/man/man3/pcre16_version.3.gz
/usr/share/man/man3/pcre32.3.gz
/usr/share/man/man3/pcre32_assign_jit_stack.3.gz
/usr/share/man/man3/pcre32_compile.3.gz
/usr/share/man/man3/pcre32_compile2.3.gz
/usr/share/man/man3/pcre32_config.3.gz
/usr/share/man/man3/pcre32_copy_named_substring.3.gz
/usr/share/man/man3/pcre32_copy_substring.3.gz
/usr/share/man/man3/pcre32_dfa_exec.3.gz
/usr/share/man/man3/pcre32_exec.3.gz
/usr/share/man/man3/pcre32_free_study.3.gz
/usr/share/man/man3/pcre32_free_substring.3.gz
/usr/share/man/man3/pcre32_free_substring_list.3.gz
/usr/share/man/man3/pcre32_fullinfo.3.gz
/usr/share/man/man3/pcre32_get_named_substring.3.gz
/usr/share/man/man3/pcre32_get_stringnumber.3.gz
/usr/share/man/man3/pcre32_get_stringtable_entries.3.gz
/usr/share/man/man3/pcre32_get_substring.3.gz
/usr/share/man/man3/pcre32_get_substring_list.3.gz
/usr/share/man/man3/pcre32_jit_exec.3.gz
/usr/share/man/man3/pcre32_jit_stack_alloc.3.gz
/usr/share/man/man3/pcre32_jit_stack_free.3.gz
/usr/share/man/man3/pcre32_maketables.3.gz
/usr/share/man/man3/pcre32_pattern_to_host_byte_order.3.gz
/usr/share/man/man3/pcre32_refcount.3.gz
/usr/share/man/man3/pcre32_study.3.gz
/usr/share/man/man3/pcre32_utf32_to_host_byte_order.3.gz
/usr/share/man/man3/pcre32_version.3.gz
/usr/share/man/man3/pcre_assign_jit_stack.3.gz
/usr/share/man/man3/pcre_compile.3.gz
/usr/share/man/man3/pcre_compile2.3.gz
/usr/share/man/man3/pcre_config.3.gz
/usr/share/man/man3/pcre_copy_named_substring.3.gz
/usr/share/man/man3/pcre_copy_substring.3.gz
/usr/share/man/man3/pcre_dfa_exec.3.gz
/usr/share/man/man3/pcre_exec.3.gz
/usr/share/man/man3/pcre_free_study.3.gz
/usr/share/man/man3/pcre_free_substring.3.gz
/usr/share/man/man3/pcre_free_substring_list.3.gz
/usr/share/man/man3/pcre_fullinfo.3.gz
/usr/share/man/man3/pcre_get_named_substring.3.gz
/usr/share/man/man3/pcre_get_stringnumber.3.gz
/usr/share/man/man3/pcre_get_stringtable_entries.3.gz
/usr/share/man/man3/pcre_get_substring.3.gz
/usr/share/man/man3/pcre_get_substring_list.3.gz
/usr/share/man/man3/pcre_jit_exec.3.gz
/usr/share/man/man3/pcre_jit_stack_alloc.3.gz
/usr/share/man/man3/pcre_jit_stack_free.3.gz
/usr/share/man/man3/pcre_maketables.3.gz
/usr/share/man/man3/pcre_pattern_to_host_byte_order.3.gz
/usr/share/man/man3/pcre_refcount.3.gz
/usr/share/man/man3/pcre_study.3.gz
/usr/share/man/man3/pcre_utf16_to_host_byte_order.3.gz
/usr/share/man/man3/pcre_utf32_to_host_byte_order.3.gz
/usr/share/man/man3/pcre_version.3.gz
/usr/share/man/man3/pcreapi.3.gz
/usr/share/man/man3/pcrebuild.3.gz
/usr/share/man/man3/pcrecallout.3.gz
/usr/share/man/man3/pcrecompat.3.gz
/usr/share/man/man3/pcrecpp.3.gz
/usr/share/man/man3/pcredemo.3.gz
/usr/share/man/man3/pcrejit.3.gz
/usr/share/man/man3/pcrelimits.3.gz
/usr/share/man/man3/pcrematching.3.gz
/usr/share/man/man3/pcrepartial.3.gz
/usr/share/man/man3/pcrepattern.3.gz
/usr/share/man/man3/pcreperform.3.gz
/usr/share/man/man3/pcreposix.3.gz
/usr/share/man/man3/pcreprecompile.3.gz
/usr/share/man/man3/pcresample.3.gz
/usr/share/man/man3/pcrestack.3.gz
/usr/share/man/man3/pcresyntax.3.gz
/usr/share/man/man3/pcreunicode.3.gz


Generated by rpm2html 1.8.1

Fabrice Bellet, Tue Jan 21 00:15:35 2020