Description of problem: rubygems >= 1.3.0 is required for Merb, the newly released ruby web framework, and thus Merb is unstallable Version-Release number of selected component (if applicable): all How reproducible: 100% Steps to Reproduce: 1. type 'gem install merb --source http://edge.merbivore.com' 2. 3. Actual results: dependency error notifying of rubygems >= 1.3.0 requirment Expected results: successful installation of merb Additional info: I tried modifying the srcrpm for 1.2x but wasn't successful. It seems that there were some changes in the setup. I also posted to fedora-devel giving a bit more context: https://www.redhat.com/archives/fedora-devel-list/2008-November/msg00424.html
Created attachment 322977 [details] Spec file for rubygems-1.3.1-1.fc9.noarch Attaching spec file for rubygems-1.3.1-1.fc9.noarch
Created attachment 322978 [details] Patch against rubygems-1.3.1.tgz for a noarch gemdir Attaching noarch patch
Created attachment 322979 [details] rubygems-1.3.1.fc9 SRPM Attaching SRPM
The above has been tested only very basically (gem list, gem update, gem install). rpmlint is silent
Thanks a lot, Jeroen. Merb 1.0 installed fine and everything seems to be working well :)
David, can I make this go to F-10 and devel at the very least? Please advice on whether or not to push it out to EL-5.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #6) > David, can I make this go to F-10 and devel at the very least? Please advice on > whether or not to push it out to EL-5. Sorry, this bz fell into some mail filter. Yes, please push this out to F-10, devel, and EL-5
rubygems-1.3.1-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/rubygems-1.3.1-1.fc10
rubygems-1.3.1-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.