Bug 2128312

Summary:	Please port your pcre dependency to pcre2. Pcre has been deprecated
Product:	[Fedora] Fedora	Reporter:	Lukas Javorsky <ljavorsk>
Component:	imapfilter	Assignee:	Andrea Veri <andrea.veri>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	38	CC:	andrea.veri, i
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	imapfilter-2.8.1-1.fc39	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-01 23:22:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2127507

Description Lukas Javorsky 2022-09-20 12:58:42 UTC

Pcre has been deprecated since Fedora 38.
Please consider porting to the new pcre2 version.

Fedora change that describes the pcre deprecation is located here: https://fedoraproject.org/wiki/PcreDeprecation
FESCo approval is located here: https://pagure.io/fesco/issue/2862

If your component has already ported to pcre2 or you don't Require/BuildRequire any pcre subpackage, feel free to close this Bugzilla.
This Bugzilla was created automatically and some issues might have occurred along the way.

Comment 1 Ben Cotton 2022-09-20 13:46:18 UTC

Adding blocking relationship to BZ 2127507 (the Change tracker)

Comment 2 Ben Cotton 2023-02-07 14:55:36 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Fedora Update System 2023-05-01 23:11:41 UTC

FEDORA-2023-44ced38a35 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-44ced38a35

Comment 4 Fedora Update System 2023-05-01 23:22:24 UTC

FEDORA-2023-44ced38a35 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.