[COOK-2322] Fix Debian init.d template

COOK-2254 left runit service broken on Debian. It was passing `:options`
hash to the template that was still expecting `:params`. Just passing
the `new_resource.options` is not a correct solution as that was meant
for runit templates and is empty by default.

This commit fixes the issue by passing and using only the service name
to the template. The runit commands are hardcoded the same way as they
already are in the provider.
Add runit-start to the boot sequence - gentoo
Update bundled runit-rpm to support Amazon Linux.

The fix provided here is identical to:
  https://github.com/imeyer/runit-rpm/pull/6
[COOK-2629] runit tests have ruby 1.9 method chaning syntax
Merge pull request #26 from tmatilai/COOK-2322_debian-initd

[COOK-2322] Fix Debian init.d template
Merge pull request #24 from psi/COOK-2545

Update bundled runit-rpm to support Amazon Linux.
release v1.1.2
Merge pull request #28 from retr0h/COOK-2629

[COOK-2629] runit tests have ruby 1.9 method chaning syntax
Add the symlinks to Gentoo platform

The service dir should contain the symlinks, and /etc/sv should contain
the original service description
Merge remote-tracking branch 'upstream/master' into COOK-2567
Move the service definition to gentoo specific section
Merge pull request #27 from pierreozoux/COOK-2567

Add runit-start to the boot sequence - gentoo
Merge pull request #29 from pierreozoux/COOK-2549-2nd-attempt

Add the symlinks to Gentoo platform
increment version for development
Updates for test-kitchen (1.0 alpha) support

* Update chef installed version to 11.4.4
* Add apt to run list on debian/ubuntu
* Add debian platform
* Make the suites test (allthethings)
* Update Gemfile to only things relevant to running specs/lint
* We don't need a vagrantfile, test-kitchen creates it
* Move test cookbooks up to test/cookbooks
* Remove Kitchenfile
* Require event_dispatch classes so rake doesn't blow up with Chef 11
[COOK-2867] - Remove the init.d file for Debian

* Update the runit_test::service recipe to have a resource that
  creates a symlink to /usr/bin/sv (this will cause a forkbomb in the
  test VM w/o the fix :-))
* On Debian, if the init.d file is a symlink, remove it so we don't
  resolve to /usr/bin/sv
* Check that the /etc/init.d/service files exist, not that they're
  symlinks, because they may be symlinks, on Debian.
release v1.1.4
Do not hardcode rpmbuild location, since there could be a problem when we call chef-client as part of OS init process
COOK-3013 block never execs if converge fails and chef-client rerun
Merge pull request #33 from sbates/COOK-3013

COOK-3013 block never execs if converge fails and chef-client rerun