Bug 2370710

Summary: Add perl-SVGPDF to EPEL 10 and 10.0
Product: [Fedora] Fedora Reporter: Petr Pisar <ppisar>
Component: perl-SVGPDFAssignee: Petr Pisar <ppisar>
Status: ASSIGNED --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jvromans
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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: 2373131, 2373137, 2373138    
Bug Blocks: 2370642    

Description Petr Pisar 2025-06-06 13:29:36 UTC
Could you please add perl-SVGPDF to EPEL 10 and 10.0? I need it there as an optional dependency for perl-PDF-Builder.

Comment 1 Petr Pisar 2025-06-17 06:27:37 UTC
If you don't have time, I could handle it if you granted me access to this package.

Comment 2 Johan Vromans 2025-06-17 06:59:56 UTC
Hi Petr, I am not familiar with making EPEL packages so please go ahead.
Let me know how I can grant you access.

Comment 3 Petr Pisar 2025-06-17 08:53:22 UTC
Thanks for the response. Please go to <https://src.fedoraproject.org/rpms/perl-SVGPDF>, log in, go to Settings → User & Groups → add user. My username is "ppisar". There you select an access level whatever you want except "ticket". That should give me access to the git repository.

Comment 4 Johan Vromans 2025-06-17 11:30:10 UTC
Done. Also for perl-File-LoadLines.

Comment 5 Petr Pisar 2025-06-17 13:16:15 UTC
It seems that the process for setting a collaborator has changed. You also need to specify what branches I have access to. I believe you did not specify "epel*" in the form as <https://src.fedoraproject.org/api/0/rpms/perl-File-LoadLines/contributors> reports no branches for me and my requests for creating the branches are rejected now.

Comment 6 Johan Vromans 2025-06-17 14:12:30 UTC
Sorry for that. It should be okay now.