Clarify the messages provided by the Debian puppet agent and master init scripts.
Merge pull request #1404 from pdxmph/master

(#18468) Further clarify messages in defaults for Debian init scripts.
(#15980) The pip provider doesn't work correctly on redhat based systems

Centos/RHEL/Fedora all use pip-python instead of pip
(#15980) Test to verify that pip-python is used on Redhat systems
(#15980) Tests to confirm functionality of the cmd function
(#15980) wrapping tests so that they're tested on both 'RedHat' and 'Not
Redhat' sytems
Merge branch 'jaredcurtis-fix/master/15980'

* jaredcurtis-fix/master/15980:
  (#15980) wrapping tests so that they're tested on both 'RedHat' and 'Not Redhat' sytems
  (#15980) Tests to confirm functionality of the cmd function
  (#15980) Test to verify that pip-python is used on Redhat systems
  (#15980) The pip provider doesn't work correctly on redhat based systems

closes: #1348
(#17777) Update debian build-depends to only use ruby1.8

Previously puppet had a build-depends of ruby, which means that on wheezy and
quantal, the default ruby of ruby1.9 was used to build puppet. Unfortunately,
this means that the shebangs for bin/puppet refer to bin/ruby1.9.1 instead of
ruby1.8. Puppet 2.7.x is installed in the ruby 1.8 specific libdir for ruby, so
ruby1.9.1 has no way of loading puppet in this case. This commit updates the
build-depends to correctly use ruby1.8 only, so bin/puppet gets the correct
ruby which can load the correct libraries.
Note: in mergeups from 2.7.x, this
needs to be undone. The build-depends of ruby is correct for puppet 3 and
later.
Merge pull request #1412 from haus/ticket/2.7.x/17777_update_build_depends

(#17777) Update debian build-depends to only use ruby1.8
Merge branch '2.7.x' into 3.0.x

Keep 3.0.x Build-Depends of ruby (not the 2.7.x Build-Depends of ruby1.8)

Conflicts:
	ext/debian/control
Merge branch '3.0.x'
(#16752) Add support for pkg.conf on openbsd

Previously only local file sources were supported for openbsd
packages. Pkg.conf is a mechanism that openbsd uses to download
packages from HTTP sources as well. This patch adds checking for
the presence of 'installpath' lines in pkg.conf and, if one
are found and if the last character of an installpath line is a
::File::SEPARATOR (aka `/` character on openbsd) then it will
become the value of the environment variable PKG_PATH previous to
pkgadd invocation, which tells pkgadd to use the URL.
(#16752) Add tests for reading installpath from /etc/pkg.conf

This commit adds tests for reading installpath from /etc/pkg.conf in the
case that a 'source' has not be specified for the package.
(#16752) Better installpath validation

Previously, if pkg.conf contained an invalid installpath, then the
openbsd package provider would accept it and set it as the package
source. For example, `installpath`, `installpath=`,
`installpath=/path`.

This commit adds better input validation, so that we only set the
package source if the regexp matches, otherwise we raise.
(#16752) Added additional tests and allow key=value

This commit adds tests to improve regexp detection. It also modifies the
regexp to accept `installpath=path`, as openbsd does not require spaces
around the equals sign.
(#16752) Refactor spec test

Previously, the spec test replicated logic for how pkgadd is invoked,
and did so inconsistently  -- whenever the resource's source ends in a
slash, the get_version method gets called which invokes `pkginfo -I
bash`.

This commit moves to two types of install expectations to helper
methods, converts the test to use `let` blocks, and sets the parameters
on the resource directly, instead of needing to define a `package`
method.