Description of problem: Please build perl-Spreadsheet-ParseExcel for EPEL 9. It's at least a build-time dependency of the perl-Spreadsheet-XLSX package. Version-Release number of selected component (if applicable): perl-Spreadsheet-ParseExcel-0.6500-30.fc35 Actual results: No perl-Spreadsheet-ParseExcel in EPEL 9. Expected results: perl-Spreadsheet-ParseExcel-0.6500-30.el9 or better ;-) Additional info: Please let me know if you are not interested in maintaining the package on EPEL 9 branch.
All dependencies of this package are now available in epel9.
Will you be able to branch and build perl-Spreadsheet-ParseExcel in epel9? I (FAS: pghmcfc) would be happy to be a co-maintainer if you do not wish to build it on epel9. I expect Robert (FAS: robert) would too since he maintains perl-Spreadsheet-XLSX. which depends on this. My interest is via perl-Finance-Quote, which depends on perl-Spreadsheet-XLSX.
Looks like a Stalled EPEL Package ticket will be needed here. Robert, do you want to co-maintain?
(In reply to Paul Howarth from comment #3) > Robert, do you want to co-maintain? Yes, makes sense due to the dependency chain.
Stalled EPEL package ticket: https://pagure.io/releng/issue/10612
Branch creation request: https://pagure.io/releng/fedora-scm-requests/issue/41779 Robert, will you do a combined build+update of this and perl-Spreadsheet-XLSX?
Branch creation is done.
FEDORA-EPEL-2022-d50ac71bb2 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d50ac71bb2
FEDORA-EPEL-2022-d50ac71bb2 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-d50ac71bb2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-d50ac71bb2 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
Needinfo email still coming, so I'm removing the flag, since the bug is now closed