For EPEL 6 - exactly 5: $ repoquery --repoid=epel-source --arch=src --whatrequires 'rubygem(rspec)' rubygem-extlib-0:0.9.13-5.el6.src rubygem-facon-0:0.4.1-2.el6.src rubygem-rack-test-0:0.5.4-1.el6.src rubygem-thin-0:1.2.8-4.el6.src rubygem-uuidtools-0:2.1.1-1.el6.src
For EPEL 5 - also 5: $ repoquery --repoid=epel-source --arch=src --whatrequires 'rubygem(rspec)' rubygem-extlib-0:0.9.13-5.el5.src rubygem-facon-0:0.4.1-2.el5.src rubygem-linode-0:0.6.2-1.el5.src rubygem-thin-0:1.2.8-2.el5.src rubygem-uuidtools-0:2.1.1-2.el5.src --Marek On 22 lip 2011, at 09:48, Vít Ondruch wrote: > RSpec 2 as they are in F16 can be imported into EPEL right now. Any idea > how many packages depends on RSpec in EPEL? > > > Vit > > > > Dne 21.7.2011 20:49, Marek Goldmann napsal(a): >> There is one more thing: >> >> Now I upgraded to RSpec 2 in Fedora. I plan to submit BoxGrinder to EPEL 6, >> but there is only RSpec 1.3. What would be the approach to bump RSpec there? >> >> --Marek >> >> On 18 lip 2011, at 18:49, Mo Morsi wrote: >> >>> Perhaps we can shoot for doing this w/ F17, and if we are unable to >>> migrate all the dependent packages over, then add a rspec1 compat >>> package to buy us some more time. >>> >>> In any case, would rather push this off to F17 myself as a few of us are >>> going through and updating alot of the rails related plugins to be >>> compatible w/ Rails 3 in Fedora. We're trying to get this done by the >>> F16 deadline next week. >> --Marek >> >> _______________________________________________ >> ruby-sig mailing list >> [email protected] >> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig > > _______________________________________________ > ruby-sig mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/ruby-sig _______________________________________________ ruby-sig mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
