Please branch and build bear in epel8. If you do not wish to maintain bear in epel8, 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/bear/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: salimma), and can be the primary contact for EPEL.
I am the current maintainer for grpc and EPEL maintainer for abseil-cpp. After some time and discussion, I decided I couldn’t package grpc for EPEL8 without compromises I wasn’t prepared to support[1]. I *think* grpc is an unconditional dependency for bear. I’m still hoping to get grpc into EPEL9, but there are nontrivial dependencies that will take some time to be ready. For example, I’d like to get the latest version of abseil-cpp into Rawhide before branching it into EPEL9 and living with it forever, but there are still some issues to work out[2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1757147 [2] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/1
I am not opposed to letting you build Bear in Epel and will give you commit rights to the epel branch if you wish to do so. However, I will not be able to help you out and I would advise you to take Ben's comments into account when making this decision.
Thanks both. With what Ben said, that looks... rather grisly. Targeting EPEL 9 might be a better idea, we're going to be on 9 at work soon anyway. Let me check back with the person that initially requested this on Monday, they mentioned they got it to build but it's painful, so I suspect he ran into the same issues as Ben (but milder as he wasn't trying to generate RPMs). I'll update then.
(In reply to Dan Čermák from comment #2) > I am not opposed to letting you build Bear in Epel and will give you commit > rights to the epel branch if you wish to do so. However, I will not be able > to help you out and I would advise you to take Ben's comments into account > when making this decision. Looping back in, I'll try and package this for EPEL 9 instead. Dan, if you could provide access, I'll work on it as soon as Ben gets abseil-cpp upgraded and branched, and grpc branched. Thanks!
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
I have requested the epel9 branch and gave you collaborator access to it. Welcome to the party and use your powers wisely ;-)
If you don’t mind, I’d like to re-open this and assign it to Michel so we can use it to track progress and dependencies.
I should have a Bodhi update with grpc for EPEL9 ready within the next day or so. There are still some missing dependencies even with grpc available, though: > No matching package to install: 'cmake(spdlog)' If you still want Bear in EPEL9, you might want to file an EPEL9 request for https://src.fedoraproject.org/rpms/spdlog.
spdlog is also available in EPEL9 now.
(In reply to Robin Lee from comment #9) > spdlog is also available in EPEL9 now. Nice. A successful build will need a buildroot override for https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f017d8e221, or to wait for it to hit stable. I did > fedpkg --release epel9 mockbuild --enablerepo=epel-testing using the current spec in Rawhide, and the build was successful. I went ahead and created a buildroot override for the grpc rebuild: https://bodhi.fedoraproject.org/overrides/grpc-1.46.3-7.el9 Michel, it looks like you can proceed.
I went ahead and started building this for EPEL9 (https://koji.fedoraproject.org/koji/taskinfo?taskID=91939180) even though Michel has not responded. Between Michel, epel-packagers-sig, and a little assistance from me if needed, any required maintenance should be covered.
FEDORA-EPEL-2022-4d02d9ec5f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4d02d9ec5f
FEDORA-EPEL-2022-4d02d9ec5f 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-4d02d9ec5f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-4d02d9ec5f has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.