Changelog for pcre-devel-static-8.45-3.1.x86_64.rpm :

* Thu Feb 29 2024 Dominique Leuenberger - Use %autosetup macro. Allows to eliminate the usage of deprecated %patchN.
* Wed May 11 2022 Jason Sikes - Added pcre-8.45-bsc1199232-unicode-property-matching.patch
* bsc#1199232
* Fixes unicode property matching issue
* Mon Jul 26 2021 Dirk Müller - update to 8.45:
* This is the final PCRE1 release. A very few small issues have been fixed.
* Mon Feb 22 2021 Andreas Schwab - Copy pcre_jit_test only if jit is enabled
* Mon Feb 15 2021 Radoslav Kolev - package testsuite in a separate RPM (boo#1182235)
* Wed Apr 15 2020 Martin Pluskal - Update to version 8.44:
* This is a bug-fix release.
* Fri Aug 02 2019 Martin Liška - Use FAT LTO objects in order to provide proper static library.
* Thu Oct 25 2018 laufferAATTph-freiburg.de- pcreposix patch taken from debian. Solves cyrus-imapd issue #1731, too. pcre-8.42-pcreposix.patch
* Tue Sep 04 2018 astiegerAATTsuse.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 bwiedemannAATTsuse.com- Do not run profiling \'check\' in parallel to make package build reproducible (boo#1040589)