Bug 1888288

Summary:	perl-EV in epel8
Product:	[Fedora] Fedora EPEL	Reporter:	jakub.jedelsky
Component:	perl-EV	Assignee:	Emmanuel Seyman <emmanuel>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	carl, emmanuel, perl-devel, ppisar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-EV-4.22-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-07 01:44:58 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:	1890590

Description jakub.jedelsky 2020-10-14 14:11:31 UTC

Hello, could you, please, build perl-EV for EPEL8? It'll help me/us to build even more perl packages. I'm able to help with it if needed, feel free to add me as a contributor.

Comment 1 Petr Pisar 2020-10-14 14:40:48 UTC

I think Carl does not maintain this package in EPEL because he has no commit access to the git repository. Emmanuel could help you including changing the Bugzilla assignee for EPEL.

Comment 2 Carl George 🎩 2020-10-14 19:49:02 UTC

I think I accidentally removed myself from this package.  I agreed in bug 1408326 to maintain the epel7 branch because at the time a coworker needed it.  I have a new job now, so I don't actually have any need for this package myself, but it's not fair to dump it on Emmanuel after agreeing to maintain it.  That said, since I don't use this package, I'm not the best person to maintain even just a branch of it.  Jakub, would you be willing to maintain the epel8 branch, and perhaps even the epel7 branch?  If not, Emmanuel please add me back to maintain the epel7 branch as I agreed, but I'm not going to maintain the epel8 branch in any case.

Side point, we now have a new permission level specifically for this called "collaborator".  You can grant commit access to branches matching a pattern, e.g. epel7 or epel*.

Comment 3 Emmanuel Seyman 2020-10-15 07:58:37 UTC

(In reply to Carl George 🤠 from comment #2):
> 
> Side point, we now have a new permission level specifically for this called
> "collaborator".

I've given you commit-level access to the perl-EV repo.

I have no objection to maintaining an EPEL8 branch for this module.
https://pagure.io/releng/fedora-scm-requests/issue/29771
https://pagure.io/releng/fedora-scm-requests/issue/29772

Comment 4 Fedora Update System 2020-10-19 18:38:54 UTC

FEDORA-EPEL-2020-da3639cc2e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-da3639cc2e

Comment 5 Fedora Update System 2020-10-20 19:47:06 UTC

FEDORA-EPEL-2020-da3639cc2e 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-2020-da3639cc2e

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

Comment 6 Fedora Update System 2020-10-22 17:51:26 UTC

FEDORA-EPEL-2020-def41e7f99 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-def41e7f99

Comment 7 Fedora Update System 2020-10-24 00:09:22 UTC

FEDORA-EPEL-2020-def41e7f99 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-2020-def41e7f99

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

Comment 8 Fedora Update System 2020-11-07 01:44:58 UTC

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