Bug 2128270

Summary:	Please port your pcre dependency to pcre2. Pcre has been deprecated
Product:	[Fedora] Fedora	Reporter:	Lukas Javorsky <ljavorsk>
Component:	anope	Assignee:	Robert Scheck <redhat-bugzilla>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anope-2.0.12-1.el9 anope-2.0.12-1.el7 anope-2.0.12-1.fc37 anope-2.0.12-1.fc36 anope-2.0.12-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-19 00:38:57 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:48:44 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 Robert Scheck 2022-09-22 12:35:36 UTC

Upstream told me on the IRC that they "try to get around to it for [Anope] 2.1".

Comment 3 Fedora Update System 2022-12-10 21:36:07 UTC

FEDORA-EPEL-2022-7804e0ae28 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-7804e0ae28

Comment 4 Fedora Update System 2022-12-10 21:36:07 UTC

FEDORA-2022-b2ef3d3a42 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b2ef3d3a42

Comment 5 Fedora Update System 2022-12-10 21:36:08 UTC

FEDORA-EPEL-2022-455e8bc5be has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-455e8bc5be

Comment 6 Fedora Update System 2022-12-10 21:36:09 UTC

FEDORA-2022-fea387b16a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fea387b16a

Comment 7 Fedora Update System 2022-12-11 02:08:07 UTC

FEDORA-2022-f65592734f has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-f65592734f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f65592734f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-12-11 02:17:40 UTC

FEDORA-2022-fea387b16a has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fea387b16a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fea387b16a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-12-11 02:21:57 UTC

FEDORA-EPEL-2022-455e8bc5be has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-455e8bc5be

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-12-11 02:30:29 UTC

FEDORA-EPEL-2022-7804e0ae28 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-7804e0ae28

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-12-11 02:30:54 UTC

FEDORA-EPEL-2022-5cd04ddcf8 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5cd04ddcf8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2022-12-11 02:37:29 UTC

FEDORA-2022-b2ef3d3a42 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b2ef3d3a42`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b2ef3d3a42

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2022-12-19 00:38:57 UTC

FEDORA-EPEL-2022-455e8bc5be has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-12-19 01:00:08 UTC

FEDORA-EPEL-2022-7804e0ae28 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-12-19 01:14:42 UTC

FEDORA-2022-b2ef3d3a42 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2022-12-19 01:17:46 UTC

FEDORA-2022-fea387b16a has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2022-12-19 01:24:00 UTC

FEDORA-EPEL-2022-5cd04ddcf8 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.