Bug 2235449 - Please branch and build mingw-pcre2 in epel9
Summary: Please branch and build mingw-pcre2 in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-pcre2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG 2226894
TreeView+ depends on / blocked
 
Reported: 2023-08-28 17:19 UTC by Davide Cavalca
Modified: 2023-09-07 00:35 UTC (History)
1 user (show)

Fixed In Version: mingw-pcre2-10.42-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-07 00:35:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Davide Cavalca 2023-08-28 17:19:19 UTC
Please branch and build mingw-pcre2 in epel9.

If you do not wish to maintain mingw-pcre2 in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/mingw-pcre2/addgroup
and grant it commit access, or collaborator access on epel* branches.

Comment 1 Fedora Update System 2023-08-29 06:02:13 UTC
FEDORA-EPEL-2023-55696b9c4e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-55696b9c4e

Comment 2 Fedora Update System 2023-08-30 01:47:50 UTC
FEDORA-EPEL-2023-55696b9c4e 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-2023-55696b9c4e

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

Comment 3 Fedora Update System 2023-09-07 00:35:46 UTC
FEDORA-EPEL-2023-55696b9c4e has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.