Latest upstream release: 1.3.1 Current version in Fedora Rawhide: 1.2.4 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.1 Current version in Fedora Rawhide: 1.2.4 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.2 Current version in Fedora Rawhide: 2.0.1 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.3 Current version in Fedora Rawhide: 2.0.1 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.4 Current version in Fedora Rawhide: 2.0.1 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.5 Current version in Fedora Rawhide: 2.0.1 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 2.0.6 Current version/release in Fedora Rawhide: 2.0.1-4.fc20 URL: http://rubygems.org/api/v1/gems/ruby2ruby.json Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Can you please do the rebase? It is blocking me into getting rubygem-safemode into Fedora.
Ping. Morsi can you do the rebase please?
rubygem-ruby2ruby-2.0.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/rubygem-ruby2ruby-2.0.6-1.fc20
Sorry somehow missed your original ping. Updated in rawhide / f20, feel free to give it karma
Package rubygem-ruby2ruby-2.0.6-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rubygem-ruby2ruby-2.0.6-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17678/rubygem-ruby2ruby-2.0.6-1.fc20 then log in and leave karma (feedback).
Hi Mo, isn't it tested enough after almost one year? ;)
rubygem-ruby2ruby-2.0.6-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.