Description of problem: octave BuildRequires glpk-devel https://src.fedoraproject.org/rpms/octave/blob/rawhide/f/octave.spec see line 95 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. cherry pick fix for finding mysql.h from https://src.fedoraproject.org/fork/trix/rpms/glpk/c/b04afaee33d18c836ab0de19aeffe77d3bfc7968?branch=epel9 to rawhide 2. fedpkg srpm 3. fedpkg scratch-build --target epel9 --srpm glpk-5.0-6.fc38.src.rpm Actual results: https://koji.fedoraproject.org/koji/taskinfo?taskID=91675969 Use in a local octave rpmbuild on rhel 9, no failures Expected results: Additional info: Add me as a project admin if you need help with epel
Will you be able to branch and build glpk in epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel9.
I am not sure what you mean, I want to get octave working on epel9, this is one of several dependencies I am working to enable of epel9. octave can work without it, but it would be good if the rawhide and epel9 octave specfiles matched when the epel9 branch was cut.
Apologies for the confusion, my comment was directed to the bug assignee and current maintainer of this package (Conrad Meyer). I also need glpk in epel9, in my case for ppl (https://bugzilla.redhat.com/show_bug.cgi?id=2121164).
Ok. We are both offering to help and both have blockers needing this package. I have collected a couple of new packages in the quest for octave support, I do not mind one more. I also don't mind if someone else wants to do the work. Like a lot of packages it mostly works as-is on rhel 9.
I have added @epel-packagers-sig.org as a collaborator with access to all epel* branches. I'll take responsibility if the primary maintainer is not happy with this action.
Not sure where that needinfo flag came from. I'll see if I can clear it....
Thank you! Branch requested: $ fedpkg request-branch epel9 https://pagure.io/releng/fedora-scm-requests/issue/47600
FEDORA-EPEL-2022-6fec4c6e57 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6fec4c6e57
FEDORA-EPEL-2022-6fec4c6e57 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-6fec4c6e57 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-6fec4c6e57 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.