Fix gem-based bootstrap on Ubuntu 14.04 and up

[leonid-shevtsov]

Fixes #373 - I was setting up another machine and finally took the time to fix the script.

libopenssl-ruby and libopenssl-ruby1.9 are both virtual packages, meaning they don't contain any files, and only instruct apt to install libruby, which is the real package. And, unlike the virtual packages, it has available on both older and newer (>14.04) systems.

I've also added a check that the package installation had succeeded.

[matschaffer]

What led to the check code? If it's something we really need I'd rather see it consistently across all installation strategies rather than just a feature for the debianoid_gem_install.

Pretty sure we have a helper in the project somewhere that also does this (i.e., runs a command fails the whole knife command if the command fails).

[matschaffer]

Oh I think I was wrong on the helper. Must have been thinking of something else.

Anyway, I'd like to have any checking code be consistent across more that just one strategy if you think it's worth including. Also

knife-solo/lib/chef/knife/solo_cook.rb

Line 315 in 6f7ae02

raise "chef-solo failed. See output above." unless result.success?

seems to be a more common pattern than just checking the exit code directly.

[leonid-shevtsov]

Maybe the run_command method should check for success itself (and add a flag to it to ignore errors)? Because after looking at the bootstrapper code, I don't see much cases when a failed command would allow the process to continue.

[matschaffer]

It will at least need some way to allow failures since I'm pretty sure it's the same function that's used to do things like check for presence of sudo, ver, etc.