Please branch and build jakarta-activation1 in epel10. If you do not wish to maintain jakarta-activation1 in epel10, 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/jakarta-activation1/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: salimma); please add me through https://src.fedoraproject.org/rpms/jakarta-activation1/adduser
Note: need to use F41 or lower branch as base because the Rawhide spec is switched over to use autosetup -C -- -C is not supported yet in EL10 COPR build: https://copr.fedorainfracloud.org/coprs/salimma/antlr4-el10/build/8232640/
Hi, I gave you personally commit access for the package. Is that enough? You can take care of the EPEL side. I do not have much experience with requesting branches for existing packages or maintaining the EPEL version of packages. But I would like to ask you to make changes via Pull Requests as much as possible instead of direct pushing.
Hi Marian. It is a bit ambiguous what your intentions were with your last comment. You changed the status to assigned and left yourself as the assignee, which indicates that you will take care of the bug. At the same time you asked Michel to take care of the bug in the comment text, which indicates that you will not take care of the bug. There are mixed signals here, so can you clarify.
Hi, by changing the status I meant to say that I am aware of it and took steps towards resolving it. The text I have written still holds. Feel free to suggest changes to the main branch to keep the dist-git branches as close as possible. And feel free to change the assignee of the bug. Do you want me to add the whole epel group as the collaborators / commiters?
Branch created: https://pagure.io/releng/fedora-scm-requests/issue/70535 PR for supported %autosetup: https://src.fedoraproject.org/rpms/jakarta-activation1/pull-request/8 Build: https://koji.fedoraproject.org/koji/taskinfo?taskID=126303102 The issue should be resolved. I can take care of the package in EPEL 10. Please let me know if there is anything more to do.
(In reply to Marián Konček from comment #5) > Please let me know if there is anything more to do. You need to create a bodhi update. EPEL 10 no longer automatically pushes new builds to stable.
FEDORA-EPEL-2024-764e4e6245 (jakarta-activation1-1.2.2-24.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-764e4e6245
FEDORA-EPEL-2024-764e4e6245 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-764e4e6245 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thank you! The request for comaintainership is optional if you can do the EPEL build, so thanks for doing both anyway (I was away most of last week, sorry for the late reply)
FEDORA-EPEL-2024-764e4e6245 (jakarta-activation1-1.2.2-24.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.