spec/spec_helper.rb | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 do not require rubygems

ext/rack/example-passenger-vhost.conf | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 set passenger puppet master document root

ext/logcheck/puppet | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix puppet-master logcheck rule

lib/puppet/provider/service/debian.rb | 29 29 + 0 - 0 !
1 file changed, 29 insertions(+)

 use /usr/sbin/service for service management on debian

In Debian jessie systemd will be the default init system. But the old system V
and other alternative init systems are still supported. /usr/sbin/service
provides an abstraction layer which is able to start, stop and restart
services independent of the init system used.

Bug: https://tickets.puppetlabs.com/browse/PUP-2023
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795

lib/puppet/provider/service/debian.rb | 95 72 + 23 - 0 !
1 file changed, 72 insertions(+), 23 deletions(-)

 [patch] fix service listing and enable/disable in debian
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add two support methods to detect when we're running systemd as PID 1
and if a service has only an initscript.

Use these to implement the following functionality:

  Under systemd, use systemctl enable/disable for all services. This
   works correctly for all types of services.

  Under systemd, use systemctl is-enabled only for services that have a
   systemd unit file and fall back to invoke-rc.d for sysv services.

Also, fix self.instances to augment the list of systemd-enabled services
with the sysv services.

Finally drop pre-2.88 sysv-rc support and use `update-rc.d enable' for
all services when running under sysv-rc, preserving order changes.

lib/puppet/rails.rb | 5 4 + 1 - 0 !
lib/puppet/rails/database/schema.rb | 20 10 + 10 - 0 !
lib/puppet/rails/fact_name.rb | 3 3 + 0 - 0 !
lib/puppet/rails/fact_value.rb | 3 3 + 0 - 0 !
lib/puppet/rails/param_value.rb | 4 2 + 2 - 0 !
lib/puppet/rails/resource_tag.rb | 4 2 + 2 - 0 !
spec/unit/rails_spec.rb | 6 3 + 3 - 0 !
7 files changed, 27 insertions(+), 18 deletions(-)

 stored configs compatibility with activerecord 4.x
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Make ActiveRecord-based stored configs work again with ActiveRecord 4.x:

  Use AR::Base.clear_active_connections! instead of
   AR::Base.verify_active_connections!

  Always call AR::Base.connection as a class method, never as an
   instance method.

  Require 'activerecord/deprecated_finders' for AR versions later than 4.1 to
   make all #find(:all) and #find_by_x methods work again.

  Silence AR's deprecation warnings. We know we are using deprecated
   finders so these warnings are just (a lot of) noise.

  Drop all ":integer => true" options passed to add_index in the
   schema. This was probably never a valid option anyway and was ignored
   until Rails 4.x, but currently causes the DB bootstrapping to fail.

lib/puppet/indirector/catalog/compiler.rb | 6 4 + 2 - 0 !
spec/unit/indirector/catalog/compiler_spec.rb | 36 32 + 4 - 0 !
2 files changed, 36 insertions(+), 6 deletions(-)

 [patch] (pup-7483) reject all fact formats except pson

Previously, an authenticated user could cause the master to execute
YAML.load on user-specified input, as well as MessagePack.unpack if the
msgpack gem was installed.

Since 3.2.2, agents have always sent facts as PSON. There is no reason
to support other formats, so reject all fact formats except PSON.

(cherry picked from commit 06d8c51367ca932b9da5d9b01958cfc0adf0f2ea)