Fedora Account System
Red Hat Associate
Red Hat Customer
Please branch and build gnuplot in epel9. If you do not wish to maintain gnuplot in epel9, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package. (FES: tdawson) Please add me through https://src.fedoraproject.org/rpms/gnuplot/adduser
gnuplot used to be in RHEL, but it is not in RHEL9. Also, it will not build in epel9 without libcerf. I have also requested that package. https://bugzilla.redhat.com/show_bug.cgi?id=2064402
libcerf has been built and has been tagged into override. I have tested and the rawhide package now builds in EPEL9 without any changes.
Thanks for testing the build, I requested the branch to be created.
Hello Troy, the branch is now created and populated. I tried a scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=84686552 and it failed with "No matching package to install: 'libcerf-devel >= 1.11'". Is there some special magic to invoke in order to use libcerf that you have built?
You need a buildroot override. Troy's expired so I extended it: https://bodhi.fedoraproject.org/overrides/libcerf-1.17-2.el9 . Run: koji wait-repo epel9-build --build=libcerf-1.17-2.el9 To make sure it is active.
Thank you Orion, this works. Sorry for not being familiar with buildroot mechanics - does that mean that the override will need to be recreated every time one needs to rebuild the package, or will the dependency get into the buildroot eventually?
FEDORA-EPEL-2022-66707cd08a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-66707cd08a
(In reply to Pavel Cahyna from comment #6) > Sorry for not being familiar with buildroot mechanics - does that mean that > the override will need to be recreated every time one needs to rebuild the > package, or will the dependency get into the buildroot eventually? When you set an override, you have to set a time limit. The package stays in the override, and available to builds, until that time limit is up. Once a package makes it into stable (the main epel9 repository) then it is automatically available in the builds, and no longer needs an override. Since a new package, or package update, needs 7 days in -testing, or +3 karma, I set my override to 7 days, thinking that would be enough. But I forgot that it often takes a day or two to get into -testing, and a day or two to get into stable. Thus, my original override wasn't long enough.
FEDORA-EPEL-2022-66707cd08a 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-66707cd08a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-66707cd08a has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.