Description of problem: rubygem-stomp is a dependency of mcollective. With mcollective 2.0.0 (current in EPEL), stomp+ssl connectors require >=1.2.0 (current is 1.2.2) of rubygem-stomp. MCollective will install and start (without a stomp+ssl connector) fine. There are no problems. If a stomp+ssl connector is configured, MCollective refuses to start and throws errors. It would be helpful if rubygem-stomp could be upgraded to 1.2.2. Thanks, Justin
Looking at the changelog: https://github.com/stompgem/stomp/blob/master/CHANGELOG.rdoc its seems to be mostly important bug fixes plus the addition on stomp 1.1 support but 1.0 support is still there. I'd like to see this to. I just verified that the 1.2.2 builds okay with out modification beyond the obvious to the .spec file in el5 and fc16.
I'm putting 1.2.2 into Fedora today. I'll them check and make sure it's all ok before putting it in EPEL. (I work at Puppet Labs, so I am very interested in ensuring mcollective and friends work well with this on EL)
rubygem-stomp-1.2.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/rubygem-stomp-1.2.2-1.fc17
rubygem-stomp-1.2.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
And el?
rubygem-stomp-1.2.2-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/rubygem-stomp-1.2.2-1.el5
rubygem-stomp-1.2.2-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/rubygem-stomp-1.2.2-1.el6
rubygem-stomp-1.2.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
rubygem-stomp-1.2.2-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.