I would appreciate if you could build perl-Data-GUID for EPEL8. I've checked that master branch builds fine there and according to my testing works. Feel free to add me as co-maintainer. This package and its dependencies are built in https://copr.fedorainfracloud.org/coprs/ignatenkobrain/gdc/packages/.
Hi Ralf, I know you don't do EPEL so I'm happy to take this one on. If you add me as co-maint at https://src.fedoraproject.org/rpms/perl-Data-GUID I can look after this and any other EPEL branches that get requested. If you set me to Bugzilla Assignee for EPEL then you won't get bothered by EPEL requests again in the future. Back when EPEL-8 got started I built a bunch of your packages for EPEL-8 as they were dependencies of other packages. At the time there was no straightforward means for setting up separate BZ contacts for EPEL but there is now. If I supplied a list of your packages that I built for EPEL, would you be willing to add me as co-maint and EPEL BZ contact? That way you'd avoid any future EPEL requests for those packages. I will of course leave the Fedora branches alone.
FAS: pghmcfc by the way.
ping?
Ralf, could you please set pghmcfc or jplesnik as 'collaborator' and set allowed branches 'el*,epel*'? Definition of Collaborator is: A user or a group with this level of access can do everything what a user/group with ticket access can do + it can commit to some branches in the project. These branches are defined here using their name or a pattern and needs to be comma separated. Some examples: master,features/* el* master,f*
(In reply to Jitka Plesnikova from comment #4) > Ralf, could you please set pghmcfc or jplesnik as 'collaborator' and set > allowed branches 'el*,epel*'? No. Ask a RHAT manager or who ever is managing EPEL, and stop molesting me. For clarity: For the 15 years, I am contributing to Fedora, I never ever agreed to supporting EPEL and never will, because RHEL is non-free.
https://pagure.io/releng/fedora-scm-requests/issue/29566 https://pagure.io/releng/fedora-scm-requests/issue/29567
FEDORA-EPEL-2020-9e6ef245e5 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9e6ef245e5
FEDORA-EPEL-2020-9e6ef245e5 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-9e6ef245e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-9e6ef245e5 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.