Hide Forgot
Description of problem: Right now in EPEL5, we are trying to fix bug 588364 which basically states that to install rubygem-hoe, we need a newer version of rubygem-rubyforge. In looking over the spec files in devel, I think we could move the rubyforge gem without causing an ABI/API compatibility in EPEL5. Would you agree? If you would like a co-maintiner in EPEL for this gem, I would be happy to help also. The current version in EPEL5 is rubygem-rubyforge-1.0.1-1.el5 Desired is rubygem(rubyforge) >= 2.0.3
Basically I don't care for packages in EPEL. So - if you apply for commit/watchbugzilla/etc acls for this package on EPEL, I will approve it. - or if you want to become the maintainer of this package on EPEL, I will release my ownership on this package. How do you think?
I accepted your commit/approveacls/etc acls on EPEL-5. Feel free to update this package on EPEL-5.
rubygem-rubyforge-2.0.3-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/rubygem-rubyforge-2.0.3-1.el5
rubygem-rubyforge-2.0.3-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rubygem-rubyforge'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/rubygem-rubyforge-2.0.3-1.el5
rubygem-rubyforge-2.0.3-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.