Description of problem: Please build rubygem-passenger for EPEL7. Branching requests are made here: https://fedoraproject.org/wiki/EPEL/epel7/Requests
Ping - Brett can you do this or shall I?
(In reply to Orion Poplawski from comment #1) > Ping - Brett can you do this or shall I? I can, it just may take me a couple days to get there. If you need it quickly, please go ahead and do the build.
It's been renamed passenger, so we should use that name.
I guess this would require maintaining libeio in EPEL7 to. Jan - I can do both if you are not interested.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Any progress on this?
Slow - I see that passenger 5.X is out, should we jump to that? I'm looking at updating to that in rawhide.
FYI - passenger 5.0.5+ uses a modified libev. I've contacted both passenger and libev about it: https://github.com/phusion/passenger/commit/a84b6ae1a64d2ae552d3e03c69d295a166200cd0#diff-8644f07c5dc22ffd1d2cae715cbbae56 http://lists.schmorp.de/pipermail/libev/2015q2/002525.html
I'm OK with patching libev to whatever is needed for passenger. I have libev in Fedora just because of Passenger.
Ignore my last comment, I was thinking about libeio, not libev...
Is it available anywhere yet? I'd prefer install RPM and test it than install gem.
Created attachment 1112055 [details] build of f49e08f in EPEL7
The problem with libev is solved at rawhide, thanks! When trying f49e08f (5.0.23, without the json patch yet) on EPEL7, the build fails though. Maybe it is because of old libuv in EPEL7?
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.