Public bug reported: Hi,
So the rubygems dependency makes me twitch since my servers can't do gem installs from remote servers (for obvious reasons). I asked upstream why it was required and he told me it was only really used by the stomp plugin because "generally stomp is provided by gems". Digging further, it turns out that if we had a remotely modern version of libstomp-ruby, that'd be perfectly sufficient for mcollective and we could drop the 'require rubygems' entirely (at least in our packages). \o/ The newer version of libstomp-ruby issue is tracked here: https://bugs.launchpad.net/ubuntu/+source/libstomp-ruby/+bug/707317 (and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598564) So, once that (or something like it is merged), in terms of mcollective, I think mcollective's dependency on libstomp-ruby should be versioned to >= 1.1.9 and then we can drop the 'require rubygems' and corresponding dependency? -- James ** Affects: mcollective (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mcollective in Ubuntu. https://bugs.launchpad.net/bugs/808446 Title: mcollective, rubygems and libstomp-ruby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mcollective/+bug/808446/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs