disable pluginsync=true by default in puppet.conf

debian/changelog

@@ -1,9 +1,13 @@
 puppet (0.25.4-3) UNRELEASED; urgency=low
 
+  [ Stig Sandbeck Mathisen ]
   * Fix "puppetmaster and puppet scripts always return 0" with patch from
     Mathias Gug, make sure return codes are actually used (Closes: #573473)
 
- -- Stig Sandbeck Mathisen <ssm@debian.org>  Fri, 12 Mar 2010 12:18:43 +0100
+  [ Micah Anderson ]
+  * Disable default puppet.conf option pluginsync=true, see puppet-common.NEWS
+
+ -- Micah Anderson <micah@debian.org>  Mon, 15 Mar 2010 18:04:17 -0400
 
 puppet (0.25.4-2) unstable; urgency=low
 

debian/puppet-common.NEWS

@@ -1,3 +1,16 @@
+puppet (0.25.4-3) unstable; urgency=low
+
+  The pluginsync=true option is no longer set in the default puppet.conf
+  that is distributed with the package. There is a spurious error that
+  is thrown when this is enabled, and you have no plugins. Most people
+  will eventually want this enabled, however for a new puppet installation
+  it tends to scare people. Given the security implications of pluginsync
+  (it can append to anything in RUBYLIB, not just puppet/facter related
+  things), it is better to have it off by default, and let you decide
+  when you want it enabled.
+
+ -- Micah Anderson <micah@debian.org>  Mon, 15 Mar 2010 18:01:15 -0400
+
 puppet (0.25.4-2) unstable; urgency=low
 
   The default location of the puppet template directory has been moved to

debian/puppet.conf

@@ -4,5 +4,4 @@ vardir=/var/lib/puppet
 ssldir=/var/lib/puppet/ssl
 rundir=/var/run/puppet
 factpath=$vardir/lib/facter
-pluginsync=true
 templatedir=$confdir/templates