Bug 2091446

Summary:	Please build PEGTL for EPEL9
Product:	[Fedora] Fedora EPEL	Reporter:	Orion Poplawski <orion>
Component:	PEGTL	Assignee:	Attila Lakatos <alakatos>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	alakatos, code, neuro-sig, rsroka, sanjay.ankur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	PEGTL-2.8.3-4.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-17 02:03:33 UTC	Type:	Bug
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:	2091152

Description Orion Poplawski 2022-05-30 00:08:32 UTC

Description of problem:

Needed for vtk.  Thanks.

Comment 1 Orion Poplawski 2022-06-11 03:16:52 UTC

If you do not want to maintain it, please add me (orion) to the package and I will do so.  Thanks.

Comment 2 Orion Poplawski 2022-06-25 03:26:09 UTC

Second ping to request access so I can build it.  Thank you.

Comment 3 Ben Beasley 2022-06-25 17:53:07 UTC

I have used my neuro-sig packaging group membership to grant you commit privileges on PEGTL.

Comment 4 Orion Poplawski 2022-06-26 03:18:28 UTC

Thanks, but I'm afraid commit privs are not enough for me to request a branch.  I would need at least collaborator rights to do that.  Or you could request the branch and I could then commit to it.

Comment 5 Ben Beasley 2022-06-26 13:20:28 UTC

(In reply to Orion Poplawski from comment #4)
> Thanks, but I'm afraid commit privs are not enough for me to request a
> branch.  I would need at least collaborator rights to do that.  Or you could
> request the branch and I could then commit to it.

Hmm, I forgot about that. The documentation implies that collaborator should be a subset of commit privileges, although it doesn’t specifically mention requesting branches.

Anyway, I’ve now requested the branch: https://pagure.io/releng/fedora-scm-requests/issue/45292

Comment 6 Orion Poplawski 2022-07-08 03:09:20 UTC

Branch has been created.  Can you do the build?  Thanks.

Comment 7 Fedora Update System 2022-07-08 15:30:56 UTC

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

Comment 8 Ben Beasley 2022-07-08 15:32:10 UTC

(In reply to Orion Poplawski from comment #6)
> Branch has been created.  Can you do the build?  Thanks.

Okay, it’s done. Further maintenance of the branch will be up to you by default.

Comment 9 Fedora Update System 2022-07-09 02:09:05 UTC

FEDORA-EPEL-2022-a8eb261d0d 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-a8eb261d0d

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

Comment 10 Orion Poplawski 2022-07-09 03:57:25 UTC

Thanks - sorry I missed the comment about handing this off when I came back to this issue.

Comment 11 Fedora Update System 2022-07-17 02:03:33 UTC

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