Latest upstream release: 1.0.5 Current version/release in rawhide: 1.0.4-2.fc26 URL: http://www.concurrent-ruby.com 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 Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11037/
An unexpected error occured creating the scratch build: please report this issue to the-new-hotness issue tracker at https://github.com/fedora-infra/the-new-hotness/issues
+1 Needed to build OBS 2.8 unstable branch.
vondruch's rubygem-concurrent-ruby-1.0.5-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=888087
Please also build for F26. Is there some chance to get a package for EPEL7?
(In reply to Raphael Groner from comment #4) > Please also build for F26. Ok, will do > Is there some chance to get a package for EPEL7? Sorry, I'm not going to maintain EPEL7, but feel free to request the EPEL7 branch.
rubygem-concurrent-ruby-1.0.5-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0805fdfa4b
rubygem-concurrent-ruby-1.0.5-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0805fdfa4b
rubygem-concurrent-ruby-1.0.5-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.