Description of problem: rubygem-hoe-2.5.0-2.el5.noarch from epel has depsolving problems --> Missing Dependency: rubygem(minitest) >= 1.4.2 is needed by package rubygem-hoe-2.5.0-2.el5.noarch (epel) rubygem-hoe-2.5.0-2.el5.noarch from epel has depsolving problems --> Missing Dependency: rubygem(gemcutter) >= 0.2.1 is needed by package rubygem-hoe-2.5.0-2.el5.noarch (epel) rubygem-hoe-2.5.0-2.el5.noarch from epel has depsolving problems --> Missing Dependency: rubygem(rubyforge) >= 2.0.3 is needed by package rubygem-hoe-2.5.0-2.el5.noarch (epel)
Hmm. My fault for missing some deps. This works on my test system, but I realized I had built some additional packages in preparation for Sinatra stuff. I have requested the packages for rubygem-minitest and rubygem-gemcutter. rubygem-rubyforge is already available in EPEL. I will keep you posted on status.
Michael, your fault is dragging in a new major version of package (apart from dragging in a ton of new dependencies). Please do not do this sort of thing in EPEL, push bugfixes only and leave this for fedora. Thank you for quick reaction though.
Putting in new version is not a problem in EPEL, if you maintain compatibility. Somehow, I just missed these two deps and am still figuring that part out. (That system has been re-imaged since then.) Normally I start with maintaining these packages for my day job and then move them to EPEL once I've been using them a while. In this case, there is obviously some variable I missed on my work systems vs. a raw EPEL repo. I am trying to fix it and have requested branches for minitest and gemcutter.
rubygem-hoe now installs fine, closing off this bug