From ssm at debian.org  Sun Mar  1 09:05:04 2015
From: ssm at debian.org (Stig Sandbeck Mathisen)
Date: Sun, 01 Mar 2015 10:05:04 +0100
Subject: [Pkg-puppet-devel] Bug#775795: Bug#775795: Patch to use
	/usr/sbin/service in Debian service-provider
In-Reply-To: <20150228131729.GA31734@marvin.ws.skroutz.gr>
 (sfid-20150228_142122_011166_CA24B5BD) (Apollon Oikonomopoulos's
 message of "Sat, 28 Feb 2015 15:17:31 +0200")
References: <87d25u7dtd.fsf@meteor.durcheinandertal.bofh>
 <54D4C65D.2080508@debian.org>
 <20150227092028.GA19012@marvin.ws.skroutz.gr>
 <20150228131729.GA31734@marvin.ws.skroutz.gr>
Message-ID: <874mq5krzz.fsf@dagon.fnord.no>

Apollon Oikonomopoulos <apoikos at debian.org> writes:

> On Fri, 27 Feb 2015 11:20:30 +0200 Apollon Oikonomopoulos <apoikos at debian.org> wrote:
>> The attached patch on top of 3.7.2-2 (hopefully) addresses all of
>> these issues (and drops support for pre-2.88 sysv-rc if you don't
>> mind). I have not tested it on a sysvinit Jessie system though, so if
>> anyone could do this it would be appreciated!
>
> I also tested it on a sysv-rc Jessie system. This is an updated
> version of the patch, marking the systemctl command as optional.
> Without this, sysv-rc Jessie systems would have the Debian provider
> blacklisted because of the missing systemctl command.

Feel free to commit the patch to the packaging repo.

-- 
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150301/4d58f902/attachment.sig>

From apoikos at debian.org  Sun Mar  1 10:53:47 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Sun, 1 Mar 2015 12:53:47 +0200
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
In-Reply-To: <20150228101047.GA3621@marvin.ws.skroutz.gr>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <85zj8n15n9.fsf@boum.org>
 <85sidrqy0u.fsf@boum.org>
 <20150228082913.GA12087@marvin.ws.skroutz.gr>
 <851tlawhcd.fsf@boum.org>
 <20150228101047.GA3621@marvin.ws.skroutz.gr>
Message-ID: <20150301105347.GB4475@marvin.ws.skroutz.gr>

On 12:10 Sat 28 Feb     , Apollon Oikonomopoulos wrote:
> Note that you have to install ruby-activerecord-deprecated-finders.

By the way, I wonder if puppetmaster-common should Recommend (or at 
least Suggest) ruby-activerecord and 
ruby-activerecord-deprecated-finders. If not, we should at least add a 
notice in README.Debian about what is needed to enable stored configs.

Cheers,
Apollon


From apoikos at debian.org  Sun Mar  1 10:44:14 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Sun, 1 Mar 2015 12:44:14 +0200
Subject: [Pkg-puppet-devel] Bug#775795: Bug#775795: Patch to use
	/usr/sbin/service in Debian service-provider
In-Reply-To: <874mq5krzz.fsf@dagon.fnord.no>
References: <87d25u7dtd.fsf@meteor.durcheinandertal.bofh>
 <54D4C65D.2080508@debian.org>
 <20150227092028.GA19012@marvin.ws.skroutz.gr>
 <20150228131729.GA31734@marvin.ws.skroutz.gr>
 <874mq5krzz.fsf@dagon.fnord.no>
Message-ID: <20150301104413.GA4475@marvin.ws.skroutz.gr>

On 10:05 Sun 01 Mar     , Stig Sandbeck Mathisen wrote:
> Feel free to commit the patch to the packaging repo.

Pushed!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150301/ac25787c/attachment.sig>

From info at hellasergo.gr  Sun Mar  1 14:59:26 2015
From: info at hellasergo.gr (Irasch Finance)
Date: Sun, 01 Mar 2015 14:59:26 +0000
Subject: [Pkg-puppet-devel] =?utf-8?q?Oferta_de_pr=C3=A9stamo=2E?=
Message-ID: <20150301145926.Horde.uldZJHvowUNYUlhguVByTw1@webmail.hellasergo.gr>

An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150301/a4e9a8dd/attachment.html>

From zeha at debian.org  Mon Mar  2 16:18:18 2015
From: zeha at debian.org (Christian Hofstaedtler)
Date: Mon, 2 Mar 2015 17:18:18 +0100
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <85bnl32kmr.fsf@boum.org>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org>
Message-ID: <20150302161818.GA88868@sx.local>

* intrigeri <intrigeri at debian.org> [150209 16:03]:
> tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's
> storeconfig feature can either use activerecord (deprecated, only
> works with activerecord 3.x, broken with activerecord 4.x) or PuppetDB
> (not packaged in Debian yet). So, currently we have a serious
> regression on the Wheezy->Jessie upgrade path.

The thing is, one really does not want to use Puppet with
storedconfigs with activerecord (it's unbearably slow).

IMO, nothing of value has been lost, and the only thing that should
probably be done is a NEWS/RelNotes entry (which likely is required
anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
yield anything working at all).

-- 
 ,''`.  Christian Hofstaedtler <zeha at debian.org>
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150302/9c49a301/attachment.sig>

From bts-link-upstream at lists.alioth.debian.org  Mon Mar  2 16:55:07 2015
From: bts-link-upstream at lists.alioth.debian.org (bts-link-upstream at lists.alioth.debian.org)
Date: Mon, 02 Mar 2015 16:55:07 -0000
Subject: [Pkg-puppet-devel] [bts-link] source package puppet
Message-ID: <20150302162902.17105.65297.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package puppet
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user bts-link-upstream at lists.alioth.debian.org

# remote status report for #769621 (http://bugs.debian.org/769621)
# Bug title: puppet: USR1 fails to trigger agent run
#  * https://tickets.puppetlabs.com/browse/PUP-1635
#  * remote status changed: Ready-for-Test -> Ready-for-Review
usertags 769621 - status-Ready-for-Test
usertags 769621 + status-Ready-for-Review

thanks


From intrigeri at debian.org  Mon Mar  2 16:55:50 2015
From: intrigeri at debian.org (intrigeri)
Date: Mon, 02 Mar 2015 17:55:50 +0100
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <20150302161818.GA88868@sx.local> (Christian Hofstaedtler's
 message of "Mon, 2 Mar 2015 17:18:18 +0100")
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
Message-ID: <85a8zv8hk9.fsf@boum.org>

Hi,

Christian Hofstaedtler wrote (02 Mar 2015 16:18:18 GMT) :
> The thing is, one really does not want to use Puppet with
> storedconfigs with activerecord (it's unbearably slow).

Thanks for sharing your opinion on this topic.

Let me share my experience and preferences. I've been using
storedconfigs with activerecord for years, and so far I can live with
the slowness. I'd love to use puppetdb instead, but so far it's not
part of Debian. As far as Jessie is concerned, I very much prefer to
go on living with that slowness, than having to install puppetdb from
a non-Debian APT repository.

Now, it can very well be that I'm part of a tiny minority of Puppet
users on Debian, and that it's not worth the risk to patch Puppet and
reintroduce the missing feature at this stage of the release process.

Cheers,
-- 
intrigeri


From micah at debian.org  Mon Mar  2 17:09:32 2015
From: micah at debian.org (micah)
Date: Mon, 02 Mar 2015 12:09:32 -0500
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <20150302161818.GA88868@sx.local>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
Message-ID: <874mq3pbqr.fsf@muck.riseup.net>

Christian Hofstaedtler <zeha at debian.org> writes:

> * intrigeri <intrigeri at debian.org> [150209 16:03]:
>> tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's
>> storeconfig feature can either use activerecord (deprecated, only
>> works with activerecord 3.x, broken with activerecord 4.x) or PuppetDB
>> (not packaged in Debian yet). So, currently we have a serious
>> regression on the Wheezy->Jessie upgrade path.
>
> The thing is, one really does not want to use Puppet with
> storedconfigs with activerecord (it's unbearably slow).

I disagree, I want to use Puppet with storedconfigs and activerecord. In
fact, I'm using it now, and have been doing so for over eight
years. Puppet has come a long way since the early days, but if you knew
how slow it was back then, you would think that storedconfigs with
activerecord was blazing fast now.

While I am interested in switching to puppetdb and getting even moar
speed, the fact that it is not possible to install puppetdb in debian
right now (and the challenges in getting it packaged are not trivial) is
pretty significant because it breaks everybody's puppet setup until that
is available, and it doesn't look like it will be available for Jessie.

> IMO, nothing of value has been lost, and the only thing that should
> probably be done is a NEWS/RelNotes entry (which likely is required
> anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
> yield anything working at all).

That is why we are adopting our manifests for the newer requirements, it
is a bit painful to do so, but it would be much more painful if our
choice was to either not upgrade to jessie, or install a non-debian
provided puppetdb.

micah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150302/607075be/attachment.sig>

From glavagetto at wikimedia.org  Tue Mar  3 07:17:02 2015
From: glavagetto at wikimedia.org (Giuseppe Lavagetto)
Date: Tue, 3 Mar 2015 08:17:02 +0100
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <874mq3pbqr.fsf@muck.riseup.net>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
 <874mq3pbqr.fsf@muck.riseup.net>
Message-ID: <CACWH4cZgPiZ+gDcVgBTDJ7_nwGG0RRuHr4+W5FczdNv+A2UnVg@mail.gmail.com>

On Mon, Mar 2, 2015 at 6:09 PM, micah <micah at debian.org> wrote:
> Christian Hofstaedtler <zeha at debian.org> writes:

[CUT]

>> The thing is, one really does not want to use Puppet with
>> storedconfigs with activerecord (it's unbearably slow).
>
> I disagree, I want to use Puppet with storedconfigs and activerecord. In
> fact, I'm using it now, and have been doing so for over eight
> years. Puppet has come a long way since the early days, but if you knew
> how slow it was back then, you would think that storedconfigs with
> activerecord was blazing fast now.
>

I agree 100% with this. But I think this is beyond the point.

>> IMO, nothing of value has been lost, and the only thing that should
>> probably be done is a NEWS/RelNotes entry (which likely is required
>> anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
>> yield anything working at all).
>
> That is why we are adopting our manifests for the newer requirements, it
> is a bit painful to do so, but it would be much more painful if our
> choice was to either not upgrade to jessie, or install a non-debian
> provided puppetdb.
>

Exactly. The point is: we're not dropping support for AR
storedconfigs, we're breaking external resources support.

if puppetdb was available in Debian no one would complain about
dropping support for AR. No one wants AR based storedconfigs because
we love them, but because we need to be able to support external
resources on a debian system without installing 3rd party software. I
don't think this is acceptable in any way.

Giuseppe


From apoikos at debian.org  Tue Mar  3 14:50:47 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 3 Mar 2015 16:50:47 +0200
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <CACWH4cZgPiZ+gDcVgBTDJ7_nwGG0RRuHr4+W5FczdNv+A2UnVg@mail.gmail.com>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
 <874mq3pbqr.fsf@muck.riseup.net>
 <CACWH4cZgPiZ+gDcVgBTDJ7_nwGG0RRuHr4+W5FczdNv+A2UnVg@mail.gmail.com>
Message-ID: <20150303145045.GA31404@marvin.ws.skroutz.gr>

Just a small update to the patch, to fix database creation.  
lib/puppet/rails/database/schema.rb contains a lot of:

  add_index <blah>, :integer => true

statements. The :integer => true option to add_index method is not documented
anywhere, not even in the earliest versions of ActiveRecord. Up to Rails 4.0[1]
it was ignored, but now it causes the application to break:
    
    stderr: Unknown key: :integer. Valid keys are: :unique, :order, :name,
            :where, :length, :internal, :using, :algorithm, :type
    
It looks like we can safely remove these options altogether, as they
were never valid in the first place. See interdiff at [2].

Regards,
Apollon

[1] https://github.com/rails/rails/commit/8fc52706c376be03f644e847d1dd357fc88ead6f

[2] interdiff:
diff --git a/lib/puppet/rails/database/schema.rb b/lib/puppet/rails/database/schema.rb
index 931a1b6..1216719 100644
--- a/lib/puppet/rails/database/schema.rb
+++ b/lib/puppet/rails/database/schema.rb
@@ -19,8 +19,8 @@ class Puppet::Rails::Schema
           t.column :updated_at, :datetime
           t.column :created_at, :datetime
         end
-        add_index :resources, :host_id, :integer => true
-        add_index :resources, :source_file_id, :integer => true
+        add_index :resources, :host_id
+        add_index :resources, :source_file_id
 
         # Thanks, mysql!  MySQL requires a length on indexes in text fields.
         # So, we provide them for mysql and handle everything else specially.
@@ -45,8 +45,8 @@ class Puppet::Rails::Schema
           t.column :updated_at, :datetime
           t.column :created_at, :datetime
         end
-        add_index :resource_tags, :resource_id, :integer => true
-        add_index :resource_tags, :puppet_tag_id, :integer => true
+        add_index :resource_tags, :resource_id
+        add_index :resource_tags, :puppet_tag_id
 
         create_table :puppet_tags do |t|
           t.column :name, :string
@@ -55,7 +55,7 @@ class Puppet::Rails::Schema
         end
 
         # Oracle automatically creates a primary key index
-        add_index :puppet_tags, :id, :integer => true if Puppet[:dbadapter] != "oracle_enhanced"
+        add_index :puppet_tags, :id if Puppet[:dbadapter] != "oracle_enhanced"
 
         create_table :hosts do |t|
           t.column :name, :string, :null => false
@@ -69,7 +69,7 @@ class Puppet::Rails::Schema
           t.column :source_file_id, :integer
           t.column :created_at, :datetime
         end
-        add_index :hosts, :source_file_id, :integer => true
+        add_index :hosts, :source_file_id
         add_index :hosts, :name
 
         create_table :fact_names do |t|
@@ -86,8 +86,8 @@ class Puppet::Rails::Schema
           t.column :updated_at, :datetime
           t.column :created_at, :datetime
         end
-        add_index :fact_values, :fact_name_id, :integer => true
-        add_index :fact_values, :host_id, :integer => true
+        add_index :fact_values, :fact_name_id
+        add_index :fact_values, :host_id
 
         create_table :param_values do |t|
           t.column :value,  :text, :null => false
@@ -97,8 +97,8 @@ class Puppet::Rails::Schema
           t.column :updated_at, :datetime
           t.column :created_at, :datetime
         end
-        add_index :param_values, :param_name_id, :integer => true
-        add_index :param_values, :resource_id, :integer => true
+        add_index :param_values, :param_name_id
+        add_index :param_values, :resource_id
 
         create_table :param_names do |t|
           t.column :name, :string, :null => false

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Storeconfigs-compatibility-with-ActiveRecord-4.patch
Type: text/x-diff
Size: 9151 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150303/03132977/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150303/03132977/attachment.sig>

From apoikos at debian.org  Tue Mar  3 15:01:48 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 3 Mar 2015 17:01:48 +0200
Subject: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <20150302161818.GA88868@sx.local>
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
Message-ID: <20150303150147.GA6534@marvin.ws.skroutz.gr>

Hi,

On Mon, 2 Mar 2015 17:18:18 +0100 Christian Hofstaedtler <zeha at debian.org> wrote:
> IMO, nothing of value has been lost, and the only thing that should
> probably be done is a NEWS/RelNotes entry (which likely is required
> anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
> yield anything working at all).

For anyone following the best practices suggested upstream during the 
2.x cycle, the 2.7 manifests should mostly work.  They certainly did for 
us (approx 100 modules, some of them rather complicated) with just a 
couple of deprecation warnings that we fixed early on. As for stored 
configs, the schema and code has not changed at all, so there is no 
reason for it not to work. My tests sofar have shown that it works as it 
should, with the - known - limitation that structured facts are not 
supported.

Personally, I wouldn't want an upgrade to Jessie force me to install an 
external dependency like PuppetDB. Furthermore, we have a custom set of 
tools developed around the stored configs database that would need 
porting to PuppetDB as well. Since upstream still provides AR-based 
stored configs in 3.7 (even though it may be marked as deprecated), my 
view is we should support it if we can. Then for Puppet 4/5/whatever we 
definitely need to provide a PuppetDB package.

Regards,
Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150303/8b54be45/attachment.sig>

From ssm at debian.org  Tue Mar  3 22:23:43 2015
From: ssm at debian.org (Stig Sandbeck Mathisen)
Date: Tue, 03 Mar 2015 23:23:43 +0100
Subject: [Pkg-puppet-devel] Bug#774643: Bug#774643: [DRE-maint] Bug#774643:
	verify_active_connections is not present in ruby-activerecord 4.1.8
In-Reply-To: <20150303150147.GA6534@marvin.ws.skroutz.gr>
 (sfid-20150303_160324_509621_62E7869B) (Apollon Oikonomopoulos's
 message of "Tue, 3 Mar 2015 17:01:48 +0200")
References: <f62038e5a37a95272bc911e0cd36a8eb@de.mcbf.net>
 <85bnl32kmr.fsf@boum.org> <20150302161818.GA88868@sx.local>
 <20150303150147.GA6534@marvin.ws.skroutz.gr>
Message-ID: <87zj7tiuts.fsf@dagon.fnord.no>

Apollon Oikonomopoulos <apoikos at debian.org> writes:

> Then for Puppet 4/5/whatever we definitely need to provide a PuppetDB
> package.

To package puppetdb while following the Debian packaging policy,
experience with packaging clojure or java apps for Debian with leiningen
and maven would be a big bonus. The learning curve is scary steep.

-- 
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150303/a87f1849/attachment.sig>

From ftpmaster at ftp-master.debian.org  Thu Mar  5 11:32:49 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 05 Mar 2015 11:32:49 +0000
Subject: [Pkg-puppet-devel] facter_2.2.0-1~bpo70+1_amd64.changes ACCEPTED
	into wheezy-backports->backports-policy, wheezy-backports
Message-ID: <E1YTU1J-0000Q5-R4@franck.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 26 Feb 2015 10:47:26 +0200
Source: facter
Binary: facter
Architecture: source all
Version: 2.2.0-1~bpo70+1
Distribution: wheezy-backports
Urgency: medium
Maintainer: Puppet Package Maintainers <pkg-puppet-devel at lists.alioth.debian.org>
Changed-By: Apollon Oikonomopoulos <apoikos at debian.org>
Description: 
 facter     - collect and display facts about the system
Closes: 682417
Changes: 
 facter (2.2.0-1~bpo70+1) wheezy-backports; urgency=medium
 .
   * Rebuild for wheezy-backports.
 .
 facter (2.2.0-1) unstable; urgency=medium
 .
   * Imported upstream release 2.2.0
 .
 facter (2.1.0-1) unstable; urgency=medium
 .
   * Imported upstream release 2.1.0
 .
 facter (2.0.1-1) unstable; urgency=medium
 .
   * Imported upstream release 2.0.1
   * Declare compliance with version 3.9.5 of the Debian Policy Manual
 .
 facter (1.7.3-1) unstable; urgency=low
 .
   * Imported upstream version 1.7.3
   * Bump standards version (no changes)
   * Update copyright format URI
 .
 facter (1.7.2-1) unstable; urgency=low
 .
   * Imported upstream version 1.7.2
 .
 facter (1.7.0-1) unstable; urgency=low
 .
   [ Micah Anderson ]
   * fix xen0/xenu detection (Closes: #682417)
 .
   [ Stig Sandbeck Mathisen ]
   * New upstream release
   * Recommend virt-what for virtualization detection
   * Update copyright information
Checksums-Sha1: 
 6a218db5de653fbc9a289928279449ee3d3550f6 2113 facter_2.2.0-1~bpo70+1.dsc
 f0fba6ce9d5ee310bbbc5f0487e6c2b5b466d439 6139 facter_2.2.0-1~bpo70+1.debian.tar.gz
 2a83d81d4a82024ba050c5eb008254fed46b537e 88780 facter_2.2.0-1~bpo70+1_all.deb
Checksums-Sha256: 
 c07971a6e2ce80187e9ceccf6b6320b7011bec5a12cdced84b128f12a0ff61ad 2113 facter_2.2.0-1~bpo70+1.dsc
 ec1ae70de417e8a3c8c972cb85777f5fb927efbf2d6819edcdc38db7ca44a4f1 6139 facter_2.2.0-1~bpo70+1.debian.tar.gz
 e4d1d8e78bf569e27a84ca7396ddf5bdd8fbaaf581742bedd6942de8160dfbae 88780 facter_2.2.0-1~bpo70+1_all.deb
Files: 
 3091ab3688be22deb767abc81ff4564f 2113 admin optional facter_2.2.0-1~bpo70+1.dsc
 d3b1d17b72fe70bd148d09b462cce83b 6139 admin optional facter_2.2.0-1~bpo70+1.debian.tar.gz
 1e3b6030848393956df96e4c8a9fedc4 88780 admin optional facter_2.2.0-1~bpo70+1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU8DkQAAoJEHLTQsHpUUMGVmIP/2xJPQlufz80EbU1KX7YS0bX
ahAbzRWMiQ53n9JNKr2S+cf+RaDbQaN4DRsuK+GzVT0Pjupz7TvOJVg94UzKMI/m
aLB4sOuDjCbyG6EciY/HtH1nm3H2SCFAJU+qkVUUjptfmUY2CPcxJdA3Jwdjn6PM
mOWQwbby3MAlBxY6T5Ui0MxaOWxgY3gfK6c+h94NwwpudagWpiqrVhH6v3nxqw8M
9PabXWD+/dQMVzRHfgTU1J2n8oKfT/1HKogKVKeiLeujhBQ8YO+9c0R40FPG1OxI
i4DLPF55e6HE2bYhXhtwzAPeiC1nxcP8Ee80DIm6HtHxohQscIgT2i03Xj5ohFMG
DhmyFxNy/Lkr2IpD6w0sYbEoN/88VfW0tCwyW7+EbMjS/twBT9R9yLH92rWi/Gy5
NrW9SGNqHtfnLTyH709gaAaudNIFuZCRBilE2xtIpMqRciB4jpYawpt0T03eSKZd
gVyOMpdnCWbMCN7/IPFqYvPBsC1IpxLqwiRV5OJSwfvmeEBqeUzdYZY/PuXRR0gT
xiVdAQsApISIYXqF+nE6BnTbukOu4V7ywj1PiAgKQ/aoe0EPuX+Sv1mz1yo9S3tU
Hh+KLAmfEYWFmsiqJGdDH3iYmb6vHrj+s52LUddx5FELQWBJmhKIZviQYCT1mNyP
4HNl+j5R3fCAZ76sy9Mi
=BaL2
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From apoikos at moszumanska.debian.org  Thu Mar  5 12:03:01 2015
From: apoikos at moszumanska.debian.org (Apollon Oikonomopoulos)
Date: Thu, 05 Mar 2015 12:03:01 +0000
Subject: [Pkg-puppet-devel] [facter] branch wheezy-backports created (now
	66fa364)
Message-ID: <20150305120259.30101.1163@moszumanska.debian.org>

This is an automated email from the git hooks/post-receive script.

apoikos pushed a change to branch wheezy-backports
in repository facter.

        at  66fa364   Rebuild 2.2.0-1 for wheezy-backports

This branch includes the following new commits:

       new  52edca7   Add self to Uploaders for the backport
       new  308dac1   Add d/gbp.conf for wheezy-backports
       new  66fa364   Rebuild 2.2.0-1 for wheezy-backports

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-puppet/facter.git


From apoikos at moszumanska.debian.org  Thu Mar  5 12:03:01 2015
From: apoikos at moszumanska.debian.org (Apollon Oikonomopoulos)
Date: Thu, 05 Mar 2015 12:03:01 +0000
Subject: [Pkg-puppet-devel] [facter] 01/03: Add self to Uploaders for the
	backport
In-Reply-To: <20150305120259.30101.1163@moszumanska.debian.org>
References: <20150305120259.30101.1163@moszumanska.debian.org>
Message-ID: <E1YTUUX-0007re-KG@moszumanska.debian.org>

This is an automated email from the git hooks/post-receive script.

apoikos pushed a commit to branch wheezy-backports
in repository facter.

commit 52edca787b9d5c88a2996642898b3c1102e780c3
Author: Apollon Oikonomopoulos <apoikos at debian.org>
Date:   Thu Feb 26 10:48:30 2015 +0200

    Add self to Uploaders for the backport
---
 debian/control | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 9bc908c..1565280 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,11 @@ Source: facter
 Section: admin
 Priority: optional
 Maintainer: Puppet Package Maintainers <pkg-puppet-devel at lists.alioth.debian.org>
-Uploaders: Andrew Pollock <apollock at debian.org>, Nigel Kersten <nigel at explanatorygap.net>, Micah Anderson <micah at debian.org>, Stig Sandbeck Mathisen <ssm at debian.org>
+Uploaders: Andrew Pollock <apollock at debian.org>,
+           Nigel Kersten <nigel at explanatorygap.net>,
+           Micah Anderson <micah at debian.org>,
+           Stig Sandbeck Mathisen <ssm at debian.org>,
+           Apollon Oikonomopoulos <apoikos at debian.org>
 Build-Depends:
  debhelper (>= 8),
  ruby | ruby-interpreter,

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-puppet/facter.git


From apoikos at moszumanska.debian.org  Thu Mar  5 12:03:01 2015
From: apoikos at moszumanska.debian.org (Apollon Oikonomopoulos)
Date: Thu, 05 Mar 2015 12:03:01 +0000
Subject: [Pkg-puppet-devel] [facter] 02/03: Add d/gbp.conf for
	wheezy-backports
In-Reply-To: <20150305120259.30101.1163@moszumanska.debian.org>
References: <20150305120259.30101.1163@moszumanska.debian.org>
Message-ID: <E1YTUUX-0007rp-N0@moszumanska.debian.org>

This is an automated email from the git hooks/post-receive script.

apoikos pushed a commit to branch wheezy-backports
in repository facter.

commit 308dac1e3955ec761be020ae052948c3c29215d7
Author: Apollon Oikonomopoulos <apoikos at debian.org>
Date:   Thu Feb 26 10:49:43 2015 +0200

    Add d/gbp.conf for wheezy-backports
    
    Default to the wheezy-backports branch and distribution.
---
 debian/gbp.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 0000000..e7c64cb
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch = wheezy-backports
+dist = wheezy-backports

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-puppet/facter.git


From apoikos at moszumanska.debian.org  Thu Mar  5 12:03:01 2015
From: apoikos at moszumanska.debian.org (Apollon Oikonomopoulos)
Date: Thu, 05 Mar 2015 12:03:01 +0000
Subject: [Pkg-puppet-devel] [facter] 03/03: Rebuild 2.2.0-1 for
	wheezy-backports
In-Reply-To: <20150305120259.30101.1163@moszumanska.debian.org>
References: <20150305120259.30101.1163@moszumanska.debian.org>
Message-ID: <E1YTUUX-0007s4-Q2@moszumanska.debian.org>

This is an automated email from the git hooks/post-receive script.

apoikos pushed a commit to branch wheezy-backports
in repository facter.

commit 66fa364e9806f48dff27bcbace8a2ac11ca80e12
Author: Apollon Oikonomopoulos <apoikos at debian.org>
Date:   Thu Feb 26 10:50:09 2015 +0200

    Rebuild 2.2.0-1 for wheezy-backports
---
 debian/changelog | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index b46ecfa..a09f22c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+facter (2.2.0-1~bpo70+1) wheezy-backports; urgency=medium
+
+  * Rebuild for wheezy-backports.
+
+ -- Apollon Oikonomopoulos <apoikos at debian.org>  Thu, 26 Feb 2015 10:47:26 +0200
+
 facter (2.2.0-1) unstable; urgency=medium
 
   * Imported upstream release 2.2.0

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-puppet/facter.git


From apoikos at moszumanska.debian.org  Thu Mar  5 12:03:01 2015
From: apoikos at moszumanska.debian.org (Apollon Oikonomopoulos)
Date: Thu, 05 Mar 2015 12:03:01 +0000
Subject: [Pkg-puppet-devel] [facter] annotated tag debian/2.2.0-1_bpo70+1
	created (now 78860b0)
Message-ID: <20150305120301.30101.68343@moszumanska.debian.org>

This is an automated email from the git hooks/post-receive script.

apoikos pushed a change to annotated tag debian/2.2.0-1_bpo70+1
in repository facter.

        at  78860b0   (tag)
   tagging  66fa364e9806f48dff27bcbace8a2ac11ca80e12 (commit)
  replaces  debian/2.2.0-1
 tagged by  Apollon Oikonomopoulos
        on  Thu Feb 26 10:51:16 2015 +0200

- Log -----------------------------------------------------------------
facter Debian release 2.2.0-1~bpo70+1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABCAAGBQJU7t6EAAoJEHLTQsHpUUMG5EoP/jAqRL+Vj370Eyit+fh9PPoz
/l3WXyj6RUOuaN4MpxVfm11NLtL3dzUAjHisDvryUMHuByKWd6dlKuL3ofeMyc36
Jwv114YG2qqqnmq3OGbt+oOHkFeeiWFO88/mZHxlN2azk3U6u4f85cQ5krsU+hfy
qJfkzefQA7HzXAA2KNmDgcKh1U/6NK2AJ9WwmTaOnu691xhhljGqfDpM1FTmK03/
vQ6JuaAaO23nLAtZMhNbav44F2Zrje9VJsJGL0V0W/6J/JXbcPjHW9y0GIEmq2sz
+zkVd4SNdPgBbXnDcV7Hcf6JEHdaB9yI3TX9bG4zU/jyPFnML5tpZ+7tffoZ6yF3
5YT1GrMgVDuE/GxoxDc/m3xPMw36gTIi6C4qwA/wIb3BNYODHMI6mwMrqJp+D575
/k9iZmSkLG87XX6q8A0Bq2W4kojDkE721tbyyLlLAIfB4ugQjOd0zl9Js1xtpVCc
0Xq8dtWDa7gaZI0ddWtfJpXbGsNQGIwCEYD6ToYKkBKbt3/3r37Uxq71kik2eawT
ZywADMqkDmCE4zxklp3vizUX4MzwT9WbYDDfkxkeMDMhrqIkaTY6d0oMA1WrpzZO
mU8gE3MsFYecDkEsWNLiWyfDsa99Lo+G799U4oaALM+4jbF1D9RgE+7RX8Sdy7ex
V8CB/K6C5K7eH6WHmMvD
=Y1B9
-----END PGP SIGNATURE-----

Apollon Oikonomopoulos (3):
      Add self to Uploaders for the backport
      Add d/gbp.conf for wheezy-backports
      Rebuild 2.2.0-1 for wheezy-backports

-----------------------------------------------------------------------

This annotated tag includes the following new commits:

       new  52edca7   Add self to Uploaders for the backport
       new  308dac1   Add d/gbp.conf for wheezy-backports
       new  66fa364   Rebuild 2.2.0-1 for wheezy-backports

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-puppet/facter.git


From bts-link-upstream at lists.alioth.debian.org  Thu Mar  5 16:54:38 2015
From: bts-link-upstream at lists.alioth.debian.org (bts-link-upstream at lists.alioth.debian.org)
Date: Thu, 05 Mar 2015 16:54:38 -0000
Subject: [Pkg-puppet-devel] [bts-link] source package puppet
Message-ID: <20150305163511.9812.65107.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package puppet
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user bts-link-upstream at lists.alioth.debian.org

# remote status report for #769621 (http://bugs.debian.org/769621)
# Bug title: puppet: USR1 fails to trigger agent run
#  * https://tickets.puppetlabs.com/browse/PUP-1635
#  * remote status changed: Ready-for-Review -> Ready-for-CI
usertags 769621 - status-Ready-for-Review
usertags 769621 + status-Ready-for-CI

thanks


From niels at thykier.net  Sun Mar  8 19:22:43 2015
From: niels at thykier.net (Niels Thykier)
Date: Sun, 08 Mar 2015 20:22:43 +0100
Subject: [Pkg-puppet-devel] [Jessie/puppet] Status on #775795 and #778891
Message-ID: <54FCA183.3050506@thykier.net>

Hi Puppet maintainers,

There are currently two remaining RC bugs against puppet, which affects
the version in Jessie.

 * #775795 - puppet: Service's debian provider assumes SysV init
 * #778891 - puppet: systemd unit file does not load environment [...]

The first is one of three blocker bugs for Jessie.  I see there is a
patch for it, which was committed to the git repository.  Do we expect
that this patch will fully solve the issue?

The second one appears to have a fairly simple patch[1]. Will this
adequately solve the issue or is there some reason not to apply it as well?


Assuming the patches are sufficient for solving the above bugs, do you
have an ETA for an upload to unstable fixing these bugs?


Thanks,
~Niels

[1]
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=puppet-environmentfile.patch;att=1;bug=778891

(Attached to original submission).



From gabster at lelutin.ca  Sun Mar  8 20:14:01 2015
From: gabster at lelutin.ca (Gabriel Filion)
Date: Sun, 08 Mar 2015 16:14:01 -0400
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
Message-ID: <54FCAD89.80705@lelutin.ca>

Hey there,

Sorry if I'm jumping in late, but I'd like to weigh in the importance of
storedconfigs. Even though it's an optional feature, the biggest
majority of users need to use it in order to have a functional setup.

For comparison, releasing without it would be like releasing apache
without one of the crucial modules, like mod_rewrite.

We really do need to find a solution to this issue before jessie is
released (or in the worst case, at first point release).

-- 
Gabriel Filion

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150308/fe0eade2/attachment.sig>

From intrigeri at debian.org  Sun Mar  8 21:16:15 2015
From: intrigeri at debian.org (intrigeri)
Date: Sun, 08 Mar 2015 22:16:15 +0100
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
In-Reply-To: <54FCAD89.80705@lelutin.ca> (Gabriel Filion's message of "Sun, 08
 Mar 2015 16:14:01 -0400")
References: <54FCAD89.80705@lelutin.ca>
Message-ID: <85pp8jur4w.fsf@boum.org>

Hi Gabriel,

Gabriel Filion wrote (08 Mar 2015 20:14:01 GMT) :
> We really do need to find a solution to this issue before jessie is
> released (or in the worst case, at first point release).

A patch series has been proposed (thanks Apollon!):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774643#90
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774643#122

=> the best way to help get this fixed is probably to test the
proposed patches and to report back here :)

Cheers,
-- 
intrigeri


From apoikos at debian.org  Mon Mar  9 11:29:11 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Mon, 9 Mar 2015 13:29:11 +0200
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
In-Reply-To: <85pp8jur4w.fsf@boum.org>
References: <54FCAD89.80705@lelutin.ca>
 <85pp8jur4w.fsf@boum.org>
Message-ID: <20150309112911.GA10414@marvin.ws.skroutz.gr>

Hi all,

On 22:16 Sun 08 Mar     , intrigeri wrote:
> => the best way to help get this fixed is probably to test the
> proposed patches and to report back here :)

By the way, we're running a production puppetmaster with the patches and 
everything (db creation, stored configs and exported resource 
collection) works fine. I'll commit the patch to the repository.

Cheers,
Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150309/b14d3ec8/attachment.sig>

From apoikos at debian.org  Mon Mar  9 15:41:49 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Mon, 9 Mar 2015 17:41:49 +0200
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
In-Reply-To: <20150309112911.GA10414@marvin.ws.skroutz.gr>
References: <54FCAD89.80705@lelutin.ca> <85pp8jur4w.fsf@boum.org>
 <20150309112911.GA10414@marvin.ws.skroutz.gr>
Message-ID: <20150309154149.GB10414@marvin.ws.skroutz.gr>

Control: severity -1 serious

Also, since all major Puppet setups I know of use AR-based stored 
configs and exported resources, I think this is a major regression from 
wheezy and warrants a severity: serious.

Regards,
Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150309/cd49dab3/attachment.sig>

From owner at bugs.debian.org  Mon Mar  9 15:45:05 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 09 Mar 2015 15:45:05 +0000
Subject: [Pkg-puppet-devel] Processed: Re: Bug#774643:
 verify_active_connections is not present in ruby-activerecord 4.1.8
References: <20150309154149.GB10414@marvin.ws.skroutz.gr>
 <20150105173833.GA14180@localhost>
Message-ID: <handler.s.B774643.142591572015798.transcript@bugs.debian.org>

Processing control commands:

> severity -1 serious
Bug #774643 [puppetmaster] Lacking support of exported resources
Severity set to 'serious' from 'important'

-- 
774643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774643
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From bts-link-upstream at lists.alioth.debian.org  Mon Mar  9 16:28:49 2015
From: bts-link-upstream at lists.alioth.debian.org (bts-link-upstream at lists.alioth.debian.org)
Date: Mon, 09 Mar 2015 16:28:49 -0000
Subject: [Pkg-puppet-devel] [bts-link] source package puppet
Message-ID: <20150309162840.9343.47697.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package puppet
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user bts-link-upstream at lists.alioth.debian.org

# remote status report for #769621 (http://bugs.debian.org/769621)
# Bug title: puppet: USR1 fails to trigger agent run
#  * https://tickets.puppetlabs.com/browse/PUP-1635
#  * remote status changed: Ready-for-CI -> Ready-for-Test
usertags 769621 - status-Ready-for-CI
usertags 769621 + status-Ready-for-Test

thanks


From zanuzzo at sifranutricao.com.br  Mon Mar  9 17:04:09 2015
From: zanuzzo at sifranutricao.com.br (ALEXANDRA HAMPEL BAER)
Date: Mon, 09 Mar 2015 14:04:09 -0300
Subject: [Pkg-puppet-devel] GOTT SEGNE EUCH
Message-ID: <20150309140409.5092812naorggjgp@www.arena.twc.com.br>



Geliebte

Heutzutage sind Gebete Wert als Gold und Diamanten. Sie sind derzeit  
in der Prozess Durststrecken ?berwinden w?rde, aber wissen, dass der  
Herr segne euch auf einem Weg, das hei?t, in Situationen, wo nur er  
kann Ihnen helfen zu glauben, bereit ist. Lassen Sie mich vorstellen,  
mein Name ist Mrs. Baer Hampel Alexandra, 15. Juli 1954 geboren. Ich  
leide an Plattenepithelkarzinom die unheilbar krank ist, ich war  
verheiratet, das hei?t, mein verstorbenen Mann Robert Joseph Edsall  
US-amerikanische Nationalit?t, herrlich und Seliger Speicher,  
beratender Ingenieur in der Republik von Benin neun Jahre lang war.  
Nach sechs Jahren Ehe starb er nach einer kurzen und einfachen 4 Tage  
der Krankheit. Mein Arzt teilte mir nur, dass meine Tage, weil mein  
Gesundheitszustand verschlechterte sich gez?hlt sind. Mein Wunsch ist  
es, eine wohlt?tige Spenden, alles, was ich von meinen verstorbenen  
Mann geerbt. Aus Angst vor Menschen der guten Sitten zu suchen, die  
dieses Geld f?r gute Zwecke einsetzen k?nnen, ich w?hlte Sie unter  
denen, dass Gott segnen wollte und dass hat warum ich mich  
entschieden, mein Erbe zu verlassen. Deshalb m?chte ich gn?dig, und um  
den Armen zu helfen, hinterlassen Sie mein Erbe in H?he mit einem Wert  
von 2.250.000 (Dollars US), sodass Sie es verwenden k?nnen, um den  
Armen, Obdachlosen, die Armen zu helfen. Ich z?hle auf Ihre  
Gesch?fts-oder Firmenwert und vor allem die ordnungsgem??e Verwendung  
der Gelder.

Gott besch?tze dich.

Frau ALEXANDRA HAMPEL BAER

Pers?nliche E-mail: baer.hampel58 at msn.com

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From ssm at debian.org  Mon Mar  9 17:55:20 2015
From: ssm at debian.org (Stig Sandbeck Mathisen)
Date: Mon, 09 Mar 2015 18:55:20 +0100
Subject: [Pkg-puppet-devel] [Jessie/puppet] Status on #775795 and #778891
In-Reply-To: <54FCA183.3050506@thykier.net>
 (sfid-20150308_203916_809584_CDBDB0B5) (Niels Thykier's message of
 "Sun, 08 Mar 2015 20:22:43 +0100")
References: <54FCA183.3050506@thykier.net>
Message-ID: <8761aa3vjr.fsf@dagon.fnord.no>

Niels Thykier <niels at thykier.net> writes:

> Hi Puppet maintainers,
>
> There are currently two remaining RC bugs against puppet, which affects
> the version in Jessie.
>
>  * #775795 - puppet: Service's debian provider assumes SysV init
>  * #778891 - puppet: systemd unit file does not load environment [...]
>
> The first is one of three blocker bugs for Jessie. I see there is a
> patch for it, which was committed to the git repository. Do we expect
> that this patch will fully solve the issue?

It passed its autopkgtests, and interactive use also worked. I'd say
"yes".

> The second one appears to have a fairly simple patch[1]. Will this
> adequately solve the issue or is there some reason not to apply it as
> well?

Apart from a distinct personal dislike of having to deal with
/etc/default/* in the future, I say the patch will solve the bug just
fine.

> Assuming the patches are sufficient for solving the above bugs, do you
> have an ETA for an upload to unstable fixing these bugs?

Assuming patches are sufficient, I should be able to upload tomorrow,
unless someone else have time to do it tonight.

-- 
Stig Sandbeck Mathisen


From niels at thykier.net  Mon Mar  9 19:30:49 2015
From: niels at thykier.net (Niels Thykier)
Date: Mon, 09 Mar 2015 20:30:49 +0100
Subject: [Pkg-puppet-devel] [Jessie/puppet] Status on #775795 and #778891
In-Reply-To: <8761aa3vjr.fsf@dagon.fnord.no>
References: <54FCA183.3050506@thykier.net> <8761aa3vjr.fsf@dagon.fnord.no>
Message-ID: <54FDF4E9.4000600@thykier.net>

On 2015-03-09 18:55, Stig Sandbeck Mathisen wrote:
> Niels Thykier <niels at thykier.net> writes:
> 
>> Hi Puppet maintainers,
>>
>> There are currently two remaining RC bugs against puppet, which affects
>> the version in Jessie.
>>
>>  * #775795 - puppet: Service's debian provider assumes SysV init
>>  * #778891 - puppet: systemd unit file does not load environment [...]
>>
>> The first is one of three blocker bugs for Jessie. I see there is a
>> patch for it, which was committed to the git repository. Do we expect
>> that this patch will fully solve the issue?
> 
> It passed its autopkgtests, and interactive use also worked. I'd say
> "yes".
> 

Good. :)

>> The second one appears to have a fairly simple patch[1]. Will this
>> adequately solve the issue or is there some reason not to apply it as
>> well?
> 
> Apart from a distinct personal dislike of having to deal with
> /etc/default/* in the future, I say the patch will solve the bug just
> fine.
> 

I could imagine.  Though, you would probably still need to keep for as
long as sysvinit is supported anyway?

>> Assuming the patches are sufficient for solving the above bugs, do you
>> have an ETA for an upload to unstable fixing these bugs?
> 
> Assuming patches are sufficient, I should be able to upload tomorrow,
> unless someone else have time to do it tonight.
> 

Excellent, looking forward to the upload. :)  Thanks for the quick response!

~Niels




From vav at ou.edu  Mon Mar  9 23:26:43 2015
From: vav at ou.edu (Vaughn, Victoria A.)
Date: Mon, 9 Mar 2015 23:26:43 +0000
Subject: [Pkg-puppet-devel] (no subject)
Message-ID: <34A3C4A692C3C84BAA9118775941AB5D01C0A0EA42@it-monad.sooner.net.ou.edu>

WE CAN GET YOU CASH TODAY!

We've helped countless of individuals, families and businesses world wide deal with their financial needs by providing them with great rates on a loan without collateral. To speak with a customer service agent today or get a loan today, email us at paydaycredits at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150309/9c3e2610/attachment-0001.html>

From apoikos at debian.org  Tue Mar 10 12:03:31 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 10 Mar 2015 14:03:31 +0200
Subject: [Pkg-puppet-devel] Bug#778891: Bug#778891: puppet: systemd unit
	file does not load environment from /etc/default/puppet -
	breaks upgrades
In-Reply-To: <54EB1CEE.9070907@esat.kuleuven.be>
References: <20150221112556.3018.54594.reportbug@mercury.esat.kuleuven.be>
 <87mw4711y3.fsf@dagon.fnord.no>
 <alpine.LRH.2.03.1502221955050.18180@esat.kuleuven.be>
 <874mqcgam0.fsf@dagon.fnord.no> <54EB1CEE.9070907@esat.kuleuven.be>
Message-ID: <20150310120330.GA1248@marvin.ws.skroutz.gr>

Hi all,

I'd like to note that since 3.2.4-1, the package's maintainer scripts 
actually _remove_ /etc/default/puppet if it's unmodified or save it as 
/etc/default/puppet.dpkg-bak if it has been modified by the user. The 
latter means that even for sysvinit users where the initscript is 
functional, upgrading from wheezy to jessie will break their setups if 
they used /etc/default/puppet to pass daemon arguments.

In my understanding to fix all of these issues the following actions are 
required:

 - change puppet.service to read /etc/default/puppet and use 
   $DAEMON_OPTS.

 - remove the dpkg-maintscript-helper rm_conffile calls from the 
   maintainer scripts. We still will not be shipping 
   /etc/default/puppet, put we don't want to remove it since the 
   initscript and the systemd unit file will be using it if it exists.

 - apart from new installations, also disable the agent when upgrading 
   from pre-3.2.4-1 versions if /etc/default/puppet exists *and* $START 
   is not true.

If so, the attached patch should? fix this bug.

Regards,
Apollon

? still untested
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 778891.diff
Type: text/x-diff
Size: 5155 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150310/517be2e5/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150310/517be2e5/attachment.sig>

From michael.weiser at gmx.de  Tue Mar 10 15:16:10 2015
From: michael.weiser at gmx.de (Michael Weiser)
Date: Tue, 10 Mar 2015 16:16:10 +0100
Subject: [Pkg-puppet-devel] ITP: puppet-module-duritong-trocla -- Use
 trocla password generator and storage from puppet.
In-Reply-To: <20150216160928.GG25179@weiser.dinsnail.net>
References: <20150212103817.GC4382@weiser.dinsnail.net>
 <20150216160928.GG25179@weiser.dinsnail.net>
Message-ID: <20150310151610.GB28907@weiser.dinsnail.net>

Hi again,

On Mon, Feb 16, 2015 at 05:09:28PM +0100, Michael Weiser wrote:

> I am making progress with the ruby package and whilst doing so have
> learned that I can login to alioth using ssh. So I guess I might be able
> to create the repo for the puppet module (and another for
> datacentered-ldap, ITP #778536) myself.

> I remember that meta.git needs to be updated to reference the new repos.

I have now created the repositories, pushed the content and adjusted
meta.git. I hope all is well. If there's no fallout I'd like to go ahead
and file ITPs for a number of other packages and add those as well.
-- 
Thanks, Michael
> A: Yes.
>> Q: Are you sure?
>>> A: Because it reverses the logical flow of conversation.
>>>> Q: Why is top posting frowned upon?


From apoikos at debian.org  Tue Mar 10 18:59:16 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 10 Mar 2015 20:59:16 +0200
Subject: [Pkg-puppet-devel] Bug#780223: unblock: puppet/3.7.2-3
Message-ID: <20150310185914.GA9993@marvin.ws.skroutz.gr>

Package: release.debian.org
Severity: normal
User: release.debian.org at packages.debian.org
Usertags: unblock

Dear Release Team,

I intend to upload puppet 3.7.2-3, fixing the #774643, #775795 and 
#778891 RC bugs and would like your pre-approval, since the list of 
changes is not small. In short, the changes introduced (grouped by bug) 
are:

 - #775795
   A patch to the Debian service provider, as attached in the bug 
   report.  This has been tested and working properly on both, sysv and 
   systemd systems.

 - #774643
   + A patch attached to the bug report, that does the minimal set of 
     changes required for puppet to work with ActiveRecord 4. The patch 
     has been tested in production without any ill side-effects. Note 
     that the patch has been slightly improved to require 
     deprecated_finders only on ActiveRecord versions that strictly need 
     it.
   + Have puppetmaster-common Recommend: ruby-activerecord and 
     ruby-activerecord-deprecated-finders. Although activerecord was not 
     in the Recommends: before, the dependency on deprecated-finders is 
     not straightforward for users to figure out and so was deemed 
     necessary to add.

 - #778891
   + A patch submitted originally with the bug report that enables the 
     systemd unit to use $DAEMON_OPTS, solving part of the issue.
   + Partial revert of an earlier decision to remove (using rm_conffile) 
     /etc/default/puppet, as the defaults file is still used by the 
     initscript and systemd unit file if present.
   + A change in puppet-common's preinst to administratively disable the 
     puppet agent when upgrading from versions where the START flag had 
     an impact. This is done to preserve the semantics of the START flag
     in the same rationale as the initial decision to disable the puppet 
     agent on fresh installs. This specific case was also discussed in 
     #778891 as having potential security implications.
   + A NEWS entry clarifying the above behavior and adding a note for
     people running puppet via cron (a rather common setup) that the 
     upgrade might administratively disable the agent.

The upload also adds upstream metadata in debian/upstream/metadata and 
fixes the Source field in debian/copyright.

See the attached debdiff for the full set of changes.

Regards,
Apollon

unblock puppet/3.7.2-3

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-------------- next part --------------
diff -Nru puppet-3.7.2/debian/changelog puppet-3.7.2/debian/changelog
--- puppet-3.7.2/debian/changelog	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/changelog	2015-03-10 19:57:24.000000000 +0200
@@ -1,3 +1,21 @@
+puppet (3.7.2-3) unstable; urgency=medium
+
+  [ Apollon Oikonomopoulos ]
+  * Team upload.
+  * Fix service enable/disable in the Debian service provider (Closes: #775795)
+  * Fix stored configs with ActiveRecord 4.x (Closes: #774643)
+    + puppetmaster-common: add Recommends for stored configs
+  * Preserve and honor changes in /etc/default/puppet (Closes: #778891)
+    + Do not remove /etc/default/puppet on upgrade
+    + Disable the agent when upgrading and START != yes
+    + puppet.service: pass $DAEMON_OPTS to puppet agent. Thanks to Rik Theys!
+    + Add a NEWS note about the START flag
+
+  [ Stig Sandbeck Mathisen ]
+  * Add upstream metadata
+
+ -- Apollon Oikonomopoulos <apoikos at debian.org>  Tue, 10 Mar 2015 14:33:45 +0200
+
 puppet (3.7.2-2) unstable; urgency=medium
 
   [ Gaudenz Steinlin ]
diff -Nru puppet-3.7.2/debian/control puppet-3.7.2/debian/control
--- puppet-3.7.2/debian/control	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/control	2015-03-10 19:57:24.000000000 +0200
@@ -81,6 +81,8 @@
  ruby | ruby-interpreter,
 Breaks: puppet (<< 0.24.7-1), puppetmaster (<< 2.7.6-1~)
 Replaces: puppet (<< 0.24.7-1), puppetmaster (<< 2.7.6-1~)
+Recommends: ruby-activerecord,
+ ruby-activerecord-deprecated-finders
 Suggests:
  apache2 | nginx,
  puppet-el,
diff -Nru puppet-3.7.2/debian/copyright puppet-3.7.2/debian/copyright
--- puppet-3.7.2/debian/copyright	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/copyright	2015-03-10 16:11:08.000000000 +0200
@@ -1,6 +1,6 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: Puppet
-Source: git://github.com/reductivelabs/puppet.git,
+Source: https://github.com/puppetlabs/puppet
 
 Files: *
 Copyright: 2004-2012 Puppet Labs Inc
diff -Nru puppet-3.7.2/debian/NEWS puppet-3.7.2/debian/NEWS
--- puppet-3.7.2/debian/NEWS	2014-11-13 13:56:19.000000000 +0200
+++ puppet-3.7.2/debian/NEWS	2015-03-10 19:57:24.000000000 +0200
@@ -1,3 +1,17 @@
+puppet (3.7.2-3) unstable; urgency=medium
+ 
+  The START flag in /etc/default/puppet is since 3.2.4-1 no longer effective.
+  To preserve state across upgrades for old setups where the puppet agent was
+  disabled using the START flag, the agent will be disabled using its built-in
+  disable facility if START is not set to true. In that case, you will need to
+  run "puppet agent --enable" before the agent can connect to a puppet master.
+
+  On systems running the puppet agent via cron, make sure that you do not rely
+  on the START variable in /etc/default/puppet and instead disable the
+  service using update-rc.d or systemctl.
+
+ -- Apollon Oikonomopoulos <apoikos at debian.org>  Tue, 10 Mar 2015 14:54:15 +0200
+
 puppet (3.2.4-1) unstable; urgency=high
 
   The puppet agent is now started by default, regardless of init system.
diff -Nru puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch
--- puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch	2015-03-10 16:11:08.000000000 +0200
@@ -0,0 +1,161 @@
+From a9b76dbfba96f537227c445297d3ccd115de46ca Mon Sep 17 00:00:00 2001
+From: Apollon Oikonomopoulos <apoikos at debian.org>
+Date: Fri, 27 Feb 2015 10:55:34 +0200
+Subject: [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/provider/service/debian.rb | 94 ++++++++++++++++++++++++++---------
+ 1 file changed, 71 insertions(+), 23 deletions(-)
+
+diff --git a/lib/puppet/provider/service/debian.rb b/lib/puppet/provider/service/debian.rb
+index 9f7a2f5..7a26409 100644
+--- a/lib/puppet/provider/service/debian.rb
++++ b/lib/puppet/provider/service/debian.rb
+@@ -15,6 +15,7 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+   # http://projects.reductivelabs.com/issues/2538
+   # is resolved.
+   commands :invoke_rc => "/usr/sbin/invoke-rc.d"
++  optional_commands :systemctl => "/bin/systemctl"
+ 
+   # This isn't being used directly, it's just here to ensure
+   # that the /usr/sbin/service binary is available.
+@@ -23,38 +24,82 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+ 
+   defaultfor :operatingsystem => :debian
+ 
++  def self.runs_on_systemd?
++    Dir.exists? "/run/systemd/system"
++  end
++
++  def is_sysv_unit?
++    # The sysv generator sets the SourcePath attribute to the name of the
++    # initscript. Use this to detect whether a unit is backed by an initscript
++    # or not.
++    source = systemctl(:show, "-pSourcePath", @resource[:name])
++    source.start_with? "SourcePath=/etc/init.d/"
++  end
++
++  def self.instances
++    # We need to merge services with systemd unit files with those only having
++    # an initscript. Note that we could use `systemctl --all` to get sysv
++    # services as well, however it would only output *enabled* services.
++    i = {}
++    if self.runs_on_systemd?
++      begin
++        output = systemctl('list-unit-files', '--type', 'service', '--full', '--all',  '--no-pager')
++        output.scan(/^(\S+)\.service\s+(disabled|enabled)\s*$/i).each do |m|
++          i[m[0]] = new(:name => m[0])
++        end
++      rescue Puppet::ExecutionFailure
++      end
++    end
++    get_services(defpath).each do |sysv|
++      unless i.has_key?(sysv.name)
++        i[sysv.name] = sysv
++      end
++    end
++    return i.values
++  end
++
+   # Remove the symlinks
+   def disable
+-    if `dpkg --compare-versions $(dpkg-query -W --showformat '${Version}' sysv-rc) ge 2.88 ; echo $?`.to_i == 0
+-      update_rc @resource[:name], "disable"
++    if self.class.runs_on_systemd?
++      systemctl(:disable, @resource[:name])
+     else
+-      update_rc "-f", @resource[:name], "remove"
+-      update_rc @resource[:name], "stop", "00", "1", "2", "3", "4", "5", "6", "."
++      update_rc @resource[:name], "disable"
+     end
+   end
+ 
+   def enabled?
+-    # TODO: Replace system call when Puppet::Util::Execution.execute gives us a way
+-    # to determine exit status.  http://projects.reductivelabs.com/issues/2538
+-    system("/usr/sbin/invoke-rc.d", "--quiet", "--query", @resource[:name], "start")
+-
+-    # 104 is the exit status when you query start an enabled service.
+-    # 106 is the exit status when the policy layer supplies a fallback action
+-    # See x-man-page://invoke-rc.d
+-    if [104, 106].include?($CHILD_STATUS.exitstatus)
+-      return :true
+-    elsif [105].include?($CHILD_STATUS.exitstatus)
+-      # 105 is unknown, which generally means the iniscript does not support query
+-      # The debian policy states that the initscript should support methods of query
+-      # For those that do not, peform the checks manually
+-      # http://www.debian.org/doc/debian-policy/ch-opersys.html
+-      if get_start_link_count >= 4
++    # Initscript-backed services have no enabled status in systemd, so we
++    # need to query them using invoke-rc.d.
++    if self.class.runs_on_systemd? and not is_sysv_unit?
++      begin
++        systemctl("is-enabled", @resource[:name])
+         return :true
+-      else
++      rescue Puppet::ExecutionFailure
+         return :false
+       end
+     else
+-      return :false
++      # TODO: Replace system call when Puppet::Util::Execution.execute gives us a way
++      # to determine exit status.  http://projects.reductivelabs.com/issues/2538
++      system("/usr/sbin/invoke-rc.d", "--quiet", "--query", @resource[:name], "start")
++
++      # 104 is the exit status when you query start an enabled service.
++      # 106 is the exit status when the policy layer supplies a fallback action
++      # See x-man-page://invoke-rc.d
++      if [104, 106].include?($CHILD_STATUS.exitstatus)
++        return :true
++      elsif [105].include?($CHILD_STATUS.exitstatus)
++        # 105 is unknown, which generally means the iniscript does not support query
++        # The debian policy states that the initscript should support methods of query
++        # For those that do not, peform the checks manually
++        # http://www.debian.org/doc/debian-policy/ch-opersys.html
++        if get_start_link_count >= 4
++          return :true
++        else
++          return :false
++        end
++      else
++        return :false
++      end
+     end
+   end
+ 
+@@ -63,8 +108,11 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+   end
+ 
+   def enable
+-    update_rc "-f", @resource[:name], "remove"
+-    update_rc @resource[:name], "defaults"
++    if self.class.runs_on_systemd?
++      systemctl(:enable, @resource[:name])
++    else
++      update_rc @resource[:name], "enable"
++    end
+   end
+ 
+   # The start, stop, restart and status command use service
+-- 
+2.1.4
+
diff -Nru puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch
--- puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	2015-03-10 19:57:24.000000000 +0200
@@ -0,0 +1,194 @@
+From 988b0aff88429f820ee247533b8aed4a77d11a62 Mon Sep 17 00:00:00 2001
+From: Apollon Oikonomopoulos <apoikos at debian.org>
+Date: Tue, 10 Mar 2015 19:46:39 +0200
+Subject: 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/rails.rb                 |  5 ++++-
+ lib/puppet/rails/database/schema.rb | 20 ++++++++++----------
+ lib/puppet/rails/fact_name.rb       |  3 +++
+ lib/puppet/rails/fact_value.rb      |  3 +++
+ lib/puppet/rails/param_value.rb     |  4 ++--
+ lib/puppet/rails/resource_tag.rb    |  4 ++--
+ 6 files changed, 24 insertions(+), 15 deletions(-)
+
+diff --git a/lib/puppet/rails.rb b/lib/puppet/rails.rb
+index 2c97c02..adb20fb 100644
+--- a/lib/puppet/rails.rb
++++ b/lib/puppet/rails.rb
+@@ -8,6 +8,9 @@ module Puppet::Rails
+   TIME_DEBUG = true
+ 
+   def self.connect
++    # Silence activerecord deprecation warnings
++    ActiveSupport::Deprecation.silenced = true
++
+     # This global init does not work for testing, because we remove
+     # the state dir on every test.
+     return if ActiveRecord::Base.connected?
+@@ -26,7 +29,7 @@ module Puppet::Rails
+     # As of ActiveRecord 2.2 allow_concurrency has been deprecated and no longer has any effect.
+     ActiveRecord::Base.allow_concurrency = true if Puppet::Util.activerecord_version < 2.2
+ 
+-    ActiveRecord::Base.verify_active_connections!
++    ActiveRecord::Base.clear_active_connections!
+ 
+     begin
+       args = database_arguments
+diff --git a/lib/puppet/rails/database/schema.rb b/lib/puppet/rails/database/schema.rb
+index 931a1b6..1216719 100644
+--- a/lib/puppet/rails/database/schema.rb
++++ b/lib/puppet/rails/database/schema.rb
+@@ -19,8 +19,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :resources, :host_id, :integer => true
+-        add_index :resources, :source_file_id, :integer => true
++        add_index :resources, :host_id
++        add_index :resources, :source_file_id
+ 
+         # Thanks, mysql!  MySQL requires a length on indexes in text fields.
+         # So, we provide them for mysql and handle everything else specially.
+@@ -45,8 +45,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :resource_tags, :resource_id, :integer => true
+-        add_index :resource_tags, :puppet_tag_id, :integer => true
++        add_index :resource_tags, :resource_id
++        add_index :resource_tags, :puppet_tag_id
+ 
+         create_table :puppet_tags do |t|
+           t.column :name, :string
+@@ -55,7 +55,7 @@ class Puppet::Rails::Schema
+         end
+ 
+         # Oracle automatically creates a primary key index
+-        add_index :puppet_tags, :id, :integer => true if Puppet[:dbadapter] != "oracle_enhanced"
++        add_index :puppet_tags, :id if Puppet[:dbadapter] != "oracle_enhanced"
+ 
+         create_table :hosts do |t|
+           t.column :name, :string, :null => false
+@@ -69,7 +69,7 @@ class Puppet::Rails::Schema
+           t.column :source_file_id, :integer
+           t.column :created_at, :datetime
+         end
+-        add_index :hosts, :source_file_id, :integer => true
++        add_index :hosts, :source_file_id
+         add_index :hosts, :name
+ 
+         create_table :fact_names do |t|
+@@ -86,8 +86,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :fact_values, :fact_name_id, :integer => true
+-        add_index :fact_values, :host_id, :integer => true
++        add_index :fact_values, :fact_name_id
++        add_index :fact_values, :host_id
+ 
+         create_table :param_values do |t|
+           t.column :value,  :text, :null => false
+@@ -97,8 +97,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :param_values, :param_name_id, :integer => true
+-        add_index :param_values, :resource_id, :integer => true
++        add_index :param_values, :param_name_id
++        add_index :param_values, :resource_id
+ 
+         create_table :param_names do |t|
+           t.column :name, :string, :null => false
+diff --git a/lib/puppet/rails/fact_name.rb b/lib/puppet/rails/fact_name.rb
+index 073bbcb..5fe5264 100644
+--- a/lib/puppet/rails/fact_name.rb
++++ b/lib/puppet/rails/fact_name.rb
+@@ -1,4 +1,7 @@
+ require 'active_record'
++if Gem::Version.new(ActiveRecord::VERSION::STRING) >= Gem::Version.new('4.1')
++  require 'active_record/deprecated_finders'
++end
+ require 'puppet/rails'
+ require 'puppet/rails/fact_value'
+ 
+diff --git a/lib/puppet/rails/fact_value.rb b/lib/puppet/rails/fact_value.rb
+index 918c0ac..d1657b9 100644
+--- a/lib/puppet/rails/fact_value.rb
++++ b/lib/puppet/rails/fact_value.rb
+@@ -1,4 +1,7 @@
+ require 'active_record'
++if Gem::Version.new(ActiveRecord::VERSION::STRING) >= Gem::Version.new('4.1')
++  require 'active_record/deprecated_finders'
++end
+ 
+ class Puppet::Rails::FactValue < ActiveRecord::Base
+   belongs_to :fact_name
+diff --git a/lib/puppet/rails/param_value.rb b/lib/puppet/rails/param_value.rb
+index d7c88f8..e082ed8 100644
+--- a/lib/puppet/rails/param_value.rb
++++ b/lib/puppet/rails/param_value.rb
+@@ -48,7 +48,7 @@ class Puppet::Rails::ParamValue < ActiveRecord::Base
+ 
+   # returns an array of hash containing all the parameters of a given resource
+   def self.find_all_params_from_resource(db_resource)
+-    params = db_resource.connection.select_all("SELECT v.id, v.value, v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN param_names n ON v.param_name_id=n.id WHERE v.resource_id=#{db_resource.id}")
++    params = ActiveRecord::Base.connection.select_all("SELECT v.id, v.value, v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN param_names n ON v.param_name_id=n.id WHERE v.resource_id=#{db_resource.id}")
+     params.each do |val|
+       val['value'] = unserialize_value(val['value'])
+       val['line'] = val['line'] ? Integer(val['line']) : nil
+@@ -59,7 +59,7 @@ class Puppet::Rails::ParamValue < ActiveRecord::Base
+ 
+   # returns an array of hash containing all the parameters of a given host
+   def self.find_all_params_from_host(db_host)
+-    params = db_host.connection.select_all("SELECT v.id, v.value,  v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN resources r ON v.resource_id=r.id INNER JOIN param_names n ON v.param_name_id=n.id WHERE r.host_id=#{db_host.id}")
++    params = ActiveRecord::Base.connection.select_all("SELECT v.id, v.value,  v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN resources r ON v.resource_id=r.id INNER JOIN param_names n ON v.param_name_id=n.id WHERE r.host_id=#{db_host.id}")
+     params.each do |val|
+       val['value'] = unserialize_value(val['value'])
+       val['line'] = val['line'] ? Integer(val['line']) : nil
+diff --git a/lib/puppet/rails/resource_tag.rb b/lib/puppet/rails/resource_tag.rb
+index 1c1aa45..1493d3e 100644
+--- a/lib/puppet/rails/resource_tag.rb
++++ b/lib/puppet/rails/resource_tag.rb
+@@ -8,7 +8,7 @@ class Puppet::Rails::ResourceTag < ActiveRecord::Base
+ 
+   # returns an array of hash containing tags of resource
+   def self.find_all_tags_from_resource(db_resource)
+-    tags = db_resource.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE t.resource_id=#{db_resource.id}")
++    tags = ActiveRecord::Base.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE t.resource_id=#{db_resource.id}")
+     tags.each do |val|
+       val['resource_id'] = Integer(val['resource_id'])
+     end
+@@ -17,7 +17,7 @@ class Puppet::Rails::ResourceTag < ActiveRecord::Base
+ 
+   # returns an array of hash containing tags of a host
+   def self.find_all_tags_from_host(db_host)
+-    tags = db_host.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN resources r ON t.resource_id=r.id INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE r.host_id=#{db_host.id}")
++    tags = ActiveRecord::Base.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN resources r ON t.resource_id=r.id INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE r.host_id=#{db_host.id}")
+     tags.each do |val|
+       val['resource_id'] = Integer(val['resource_id'])
+     end
+-- 
+2.1.4
+
diff -Nru puppet-3.7.2/debian/patches/series puppet-3.7.2/debian/patches/series
--- puppet-3.7.2/debian/patches/series	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/patches/series	2015-03-10 16:11:08.000000000 +0200
@@ -2,3 +2,5 @@
 0002-Set-passenger-puppet-master-document-root.patch
 0003-fix-puppet-master-logcheck-rule.patch
 0004-debian-service-provider-use-service.patch
+0005-Fix-service-listing-and-enable-disable-in-Debian.patch
+0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch
diff -Nru puppet-3.7.2/debian/puppet-common.preinst puppet-3.7.2/debian/puppet-common.preinst
--- puppet-3.7.2/debian/puppet-common.preinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet-common.preinst	2015-03-10 19:57:24.000000000 +0200
@@ -18,7 +18,7 @@
     tmp_lockfile=$(mktemp /var/lib/puppet/state/agent_disabled.lock.XXXXXXXX)
     lockfile=/var/lib/puppet/state/agent_disabled.lock
 
-    printf '{"disabled_message":"Disabled by default on new installations"}' \
+    printf '{"disabled_message":"Disabled by default on new or unconfigured old installations"}' \
         > $tmp_lockfile
 
     mv $tmp_lockfile $lockfile
@@ -29,10 +29,33 @@
         # disable the puppet agent on the first install
         if [ -z "$2" ]; then
             disable_puppet_agent
+        elif dpkg --compare-versions "$2" lt "3.2.4-1~" && \
+            [ -e "/etc/default/puppet" ]; then
+            # Also disable puppet if we use conffiles from a version where the
+            # START flag mattered.
+            . /etc/default/puppet
+
+            if [ "x$START" != "xtrue" -a "x$START" != "xyes" -a "x$START" != "x0" ]; then
+                # Note that "0" is not a typo, it reflects the checks done
+                # in wheezy's initscript.
+                disable_puppet_agent
+            fi
         fi
         ;;
 
     upgrade)
+        # Disable puppet if we are upgrading from a version where the START
+        # flag mattered.
+        if dpkg --compare-versions "$2" lt "3.2.4-1~" && \
+            [ -e "/etc/default/puppet" ]; then
+            . /etc/default/puppet
+
+            if [ "x$START" != "xtrue" -a "x$START" != "xyes" -a "x$START" != "x0" ]; then
+                # Note that "0" is not a typo, it reflects the checks done
+                # in wheezy's initscript.
+                disable_puppet_agent
+            fi
+        fi
         ;;
 
     abort-upgrade)
diff -Nru puppet-3.7.2/debian/puppet.postinst puppet-3.7.2/debian/puppet.postinst
--- puppet-3.7.2/debian/puppet.postinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.postinst	1970-01-01 02:00:00.000000000 +0200
@@ -1,44 +0,0 @@
-#!/bin/sh
-# postinst script for puppet
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <postinst> `configure' <most-recently-configured-version>
-#        * <old-postinst> `abort-upgrade' <new version>
-#        * <conflictor's-postinst> `abort-remove' `in-favour' <package>
-#          <new-version>
-#        * <postinst> `abort-remove'
-#        * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-#          <failed-install-package> <version> `removing'
-#          <conflicting-package> <version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    configure)
-    ;;
-
-    abort-upgrade|abort-remove|abort-deconfigure)
-    ;;
-
-    *)
-        echo "postinst called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-if dpkg-maintscript-helper supports rm_conffile; then
-    dpkg-maintscript-helper rm_conffile \
-        /etc/default/puppet 3.2.3-1 puppet -- "$@"
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.postrm puppet-3.7.2/debian/puppet.postrm
--- puppet-3.7.2/debian/puppet.postrm	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.postrm	1970-01-01 02:00:00.000000000 +0200
@@ -1,42 +0,0 @@
-#!/bin/sh
-# postrm script for puppet
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <postrm> `remove'
-#        * <postrm> `purge'
-#        * <old-postrm> `upgrade' <new-version>
-#        * <new-postrm> `failed-upgrade' <old-version>
-#        * <new-postrm> `abort-install'
-#        * <new-postrm> `abort-install' <old-version>
-#        * <new-postrm> `abort-upgrade' <old-version>
-#        * <disappearer's-postrm> `disappear' <overwriter>
-#          <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
-        if dpkg-maintscript-helper supports rm_conffile; then
-            dpkg-maintscript-helper rm_conffile \
-                /etc/default/puppet 3.2.3-1 puppet -- "$@"
-        fi
-
-    ;;
-
-    *)
-        echo "postrm called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.preinst puppet-3.7.2/debian/puppet.preinst
--- puppet-3.7.2/debian/puppet.preinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.preinst	1970-01-01 02:00:00.000000000 +0200
@@ -1,40 +0,0 @@
-#!/bin/sh
-# preinst script for #PACKAGE#
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <new-preinst> `install'
-#        * <new-preinst> `install' <old-version>
-#        * <new-preinst> `upgrade' <old-version>
-#        * <old-preinst> `abort-upgrade' <new-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    install|upgrade)
-    ;;
-
-    abort-upgrade)
-    ;;
-
-    *)
-        echo "preinst called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-if dpkg-maintscript-helper supports rm_conffile; then
-    dpkg-maintscript-helper rm_conffile \
-        /etc/default/puppet 3.2.3-1 puppet -- "$@"
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.service puppet-3.7.2/debian/puppet.service
--- puppet-3.7.2/debian/puppet.service	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.service	2015-03-10 19:57:24.000000000 +0200
@@ -3,8 +3,9 @@
 
 [Service]
 Type=forking
+EnvironmentFile=-/etc/default/puppet
 PIDFile=/run/puppet/agent.pid
-ExecStart=/usr/bin/puppet agent
+ExecStart=/usr/bin/puppet agent $DAEMON_OPTS
 
 [Install]
 WantedBy=multi-user.target
diff -Nru puppet-3.7.2/debian/upstream/metadata puppet-3.7.2/debian/upstream/metadata
--- puppet-3.7.2/debian/upstream/metadata	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/upstream/metadata	2015-03-10 16:11:08.000000000 +0200
@@ -0,0 +1,4 @@
+---
+Bug-Database: https://tickets.puppetlabs.com/browse/PUP
+Repository: https://github.com/puppetlabs/puppet.git
+Repository-Browse: https://github.com/puppetlabs/puppet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150310/24c4f0a7/attachment-0001.sig>

From bertagaz at ptitcanardnoir.org  Wed Mar 11 11:17:48 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Wed, 11 Mar 2015 12:17:48 +0100
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
Message-ID: <20150311111748.GA3852@localhost>

Hi,

> > => the best way to help get this fixed is probably to test the
> > proposed patches and to report back here :)

> By the way, we're running a production puppetmaster with the patches and 
> everything (db creation, stored configs and exported resource 
> collection) works fine. I'll commit the patch to the repository.

I've just build the puppet* packages from Jessie with the last patch from this
thread, then installed it as well as the ruby dependencies on our (Jessie)
puppetmaster.

So far it seems to work correctly (which was not the case with the first
proposed patch). The exported resources seem to be collected and deployed, e.g
the puppet-sshkeys module which uses storeconfig works now and correctly deploy
its fancy stuffs.

So I think we're in the good direction to solve this issue. Still I'd prefer to
wait for Intrigeri to review my tests before adopting this patch. If any other
can test it, please do so.

> By the way, I wonder if puppetmaster-common should Recommend (or at 
> least Suggest) ruby-activerecord and 
> ruby-activerecord-deprecated-finders. If not, we should at least add a 
> notice in README.Debian about what is needed to enable stored configs.

Yes, I believe it should Suggest them, and *also* deserve some explanations in
the README. There's no dependencies between
ruby-activerecord-deprecated-finders and ruby-activerecord, so we should make
it clear one has to install the former for the storeconfig option to work.

Also I'm not sure the patch should remove the deprecation warnings.

Thanks for your work on that!

bert.


From intrigeri at debian.org  Thu Mar 12 08:26:24 2015
From: intrigeri at debian.org (intrigeri)
Date: Thu, 12 Mar 2015 09:26:24 +0100
Subject: [Pkg-puppet-devel] Bug#774643: verify_active_connections is not
	present in ruby-activerecord 4.1.8
In-Reply-To: <20150311111748.GA3852@localhost> (bertagaz@ptitcanardnoir.org's
 message of "Wed, 11 Mar 2015 12:17:48 +0100")
References: <20150311111748.GA3852@localhost>
Message-ID: <8561a6bozz.fsf@boum.org>

bertagaz wrote (11 Mar 2015 11:17:48 GMT) :
> I've just build the puppet* packages from Jessie with the last patch from this
> thread,

Great news that you confirm it works!

> If any other can test it, please do so.

I believe it would be more beneficial to test the patch that was
attached to the (accepted) unblock request: #780223. I suspect Apollon
will upload to sid shortly, so it'll get easier to test things.

Cheers,
-- 
intrigeri


From ftpmaster at ftp-master.debian.org  Thu Mar 12 10:35:13 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 12 Mar 2015 10:35:13 +0000
Subject: [Pkg-puppet-devel] Processing of puppet_3.7.2-3_amd64.changes
Message-ID: <E1YW0SQ-0000UQ-B8@coccia.debian.org>

puppet_3.7.2-3_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
  puppet_3.7.2-3.dsc
  puppet_3.7.2-3.debian.tar.xz
  puppet-common_3.7.2-3_all.deb
  puppet_3.7.2-3_all.deb
  puppetmaster-common_3.7.2-3_all.deb
  puppetmaster_3.7.2-3_all.deb
  puppetmaster-passenger_3.7.2-3_all.deb
  vim-puppet_3.7.2-3_all.deb
  puppet-el_3.7.2-3_all.deb
  puppet-testsuite_3.7.2-3_all.deb

Greetings,

	Your Debian queue daemon (running on host coccia.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Mar 12 10:36:01 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 12 Mar 2015 10:36:01 +0000
Subject: [Pkg-puppet-devel] Processing of puppet_3.7.2-3_amd64.changes
Message-ID: <E1YW0TB-0004FN-GV@franck.debian.org>

puppet_3.7.2-3_amd64.changes uploaded successfully to localhost
along with the files:
  puppet_3.7.2-3.dsc
  puppet_3.7.2-3.debian.tar.xz
  puppet-common_3.7.2-3_all.deb
  puppet_3.7.2-3_all.deb
  puppetmaster-common_3.7.2-3_all.deb
  puppetmaster_3.7.2-3_all.deb
  puppetmaster-passenger_3.7.2-3_all.deb
  vim-puppet_3.7.2-3_all.deb
  puppet-el_3.7.2-3_all.deb
  puppet-testsuite_3.7.2-3_all.deb

Greetings,

	Your Debian queue daemon (running on host franck.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Mar 12 10:49:04 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 12 Mar 2015 10:49:04 +0000
Subject: [Pkg-puppet-devel] puppet_3.7.2-3_amd64.changes ACCEPTED into
	unstable
Message-ID: <E1YW0fo-0007ag-Jq@franck.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 10 Mar 2015 14:33:45 +0200
Source: puppet
Binary: puppet-common puppet puppetmaster-common puppetmaster puppetmaster-passenger vim-puppet puppet-el puppet-testsuite
Architecture: source all
Version: 3.7.2-3
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers <pkg-puppet-devel at lists.alioth.debian.org>
Changed-By: Apollon Oikonomopoulos <apoikos at debian.org>
Description:
 puppet     - configuration management system, agent
 puppet-common - configuration management system
 puppet-el  - syntax highlighting for puppet manifests in emacs
 puppet-testsuite - configuration management system, development test suite
 puppetmaster - configuration management system, master service
 puppetmaster-common - configuration management system, master common files
 puppetmaster-passenger - configuration management system, scalable master service
 vim-puppet - syntax highlighting for puppet manifests in vim
Closes: 774643 775795 778891
Changes:
 puppet (3.7.2-3) unstable; urgency=medium
 .
   [ Apollon Oikonomopoulos ]
   * Team upload.
   * Fix service enable/disable in the Debian service provider (Closes: #775795)
   * Fix stored configs with ActiveRecord 4.x (Closes: #774643)
     + puppetmaster-common: add Recommends for stored configs
     + Mention stored configs dependencies in README.Debian. Also add a
       note for the deprecation of AR-based stored configs.
   * Preserve and honor changes in /etc/default/puppet (Closes: #778891)
     + Do not remove /etc/default/puppet on upgrade
     + Disable the agent when upgrading and START != yes
     + puppet.service: pass $DAEMON_OPTS to puppet agent. Thanks to Rik Theys!
     + Add a NEWS note about the START flag
 .
   [ Stig Sandbeck Mathisen ]
   * Add upstream metadata
Checksums-Sha1:
 af8de0aa810bc573b0d81a3943861126f8c02d7d 2505 puppet_3.7.2-3.dsc
 29832d3c21768bde28bedc4a0116da059ac5a562 42964 puppet_3.7.2-3.debian.tar.xz
 f93eb13077f53ec3c560419c96dac5dfccac5c50 1010188 puppet-common_3.7.2-3_all.deb
 f21c7bb9819337776de34cd0df10bce115402403 25650 puppet_3.7.2-3_all.deb
 bb4856f15d1eca2f19bc43518cd269c568a471b6 26182 puppetmaster-common_3.7.2-3_all.deb
 49e1e26799f6fe4b48c6e812c7d912ffe08c2f92 24994 puppetmaster_3.7.2-3_all.deb
 fde9693717e39fba19d9d80c573e2a1530cc6ee7 25802 puppetmaster-passenger_3.7.2-3_all.deb
 22f74511d9acf36f14a276739c4b3dd2756b6316 26006 vim-puppet_3.7.2-3_all.deb
 ae705ffd13a428e829a554db97d8f40571246a87 27446 puppet-el_3.7.2-3_all.deb
 c19e89c5622f564354de80af83a3e83fabed3fcb 804368 puppet-testsuite_3.7.2-3_all.deb
Checksums-Sha256:
 51d4d5483e01bd6646d8bc182bdb12ca771eb92b0cc82b86ba97b10fe7f2b4b0 2505 puppet_3.7.2-3.dsc
 6c326ca4a26fa643b79bb39602b9230691a2dbaf21bcb729f0117bb34ab4c40d 42964 puppet_3.7.2-3.debian.tar.xz
 59d43db2d2afd1944f7aaecaef252c1a814fdc011f05bacf30b891cdbf544564 1010188 puppet-common_3.7.2-3_all.deb
 e6d3cb54545236a9caa08dcb9bc95df1303ba97a0cab75fd21b23b504d305722 25650 puppet_3.7.2-3_all.deb
 c2c97f45890b7aa6216e58f00b6961229afe6cb5579744d9931264ffe6af7e22 26182 puppetmaster-common_3.7.2-3_all.deb
 54e77c87b562f8051993a6dab33ed6c643ea1cb123f09787a250d6a8223fc75f 24994 puppetmaster_3.7.2-3_all.deb
 2d4be5e46d094715fc613b99ece0fb6519be4f01a2760d5426d0e7e38bb7b053 25802 puppetmaster-passenger_3.7.2-3_all.deb
 0c921449229539d32648c05964f1bf37cbf89e37d9605c165d973b7d72884678 26006 vim-puppet_3.7.2-3_all.deb
 2932fce6ba83ce76db5f2fa3609c6fd6e33f8e95421287415b7e9a548edd8d3e 27446 puppet-el_3.7.2-3_all.deb
 34ecd539c828ff7699cf0d11b338ef9d3e719d68d585e1e90a8c17b44014cc6f 804368 puppet-testsuite_3.7.2-3_all.deb
Files:
 f33ab37a09e2cfac42ff2190228ec48d 2505 admin optional puppet_3.7.2-3.dsc
 be9f83528e5d83ab2bbf22a827fcdbea 42964 admin optional puppet_3.7.2-3.debian.tar.xz
 ea989f855c22aaf56f8e9862bc441954 1010188 admin optional puppet-common_3.7.2-3_all.deb
 eb90733f88b84a6b51c8a9d9c29beb98 25650 admin optional puppet_3.7.2-3_all.deb
 6181f6f3e73290d9f8402c5e2097148d 26182 admin optional puppetmaster-common_3.7.2-3_all.deb
 c17842eeb9c08222d52799560f90d110 24994 admin optional puppetmaster_3.7.2-3_all.deb
 24597a8c9b797a792acdafb27ed3462e 25802 admin optional puppetmaster-passenger_3.7.2-3_all.deb
 a8adbf2b4706c49d5812e30961a1e2e7 26006 admin optional vim-puppet_3.7.2-3_all.deb
 0e7e4fe6a27a68099dc6e6bd79c143fe 27446 admin optional puppet-el_3.7.2-3_all.deb
 80aef10d1aa3874ccf2442d88af208d7 804368 admin optional puppet-testsuite_3.7.2-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVAWElAAoJEHLTQsHpUUMGpGIP/3KdM6mwVcwh/xzzrBKtyGez
yjiqYrmGd1p9GmMAOXjbyzP163Qvn2m3yNhDqvKzetmVWs6X+kNWqOH/24hWgPug
4ib4dVreE8ioBgnEe+nY01JLMcNWYgZyIfNS6nUQrPlDcY2GY9SPTcHF0OMlC28Q
KN1bNcy1YJSrRRKGkVFaxqZuRFqZ4Zzu7yLXIq481UAdUSDp9TA9dTRkdzs6ApGU
2rjD8qWudkesbmgl1/biUlq10KSQi2r/gzwxvg+2ZxQ/8DLBeFch1fiae9C32w9X
96vN221wBlcbOBhC9BqvgThmHk/AYNmXu4bgKFmLA0iHy2/GMpMsdC+saReXpHXs
kcrTlJKgBsHtVGMlOBzawyS8i4F+87pH1MlRuVTp7bCJA6FwJyrQ2d2wO53vDBSo
VBERKFoGJt7TKHrluMMwt1PuTyF4wvXA5JeIRs85r0pV1nn5ccunScjcGEL3x85C
7kjOiJ6ErkEPxe/NE2CDvqUu3fLdByZD+w3uzLiK6p7sihhnsOmjDCvzblh8HpVm
baansFVQuYvKuOb3GmbK/d3KXw7/NK1UbLtJ8hrhNe7N2yl+f5wz+zl1/28Bo7gI
U81+ZwbGzxwShFpI11s2Ltyc6bjacRuI5fj0qsUXwCvxlmeOcjThIzfFzt4H9Bbk
WinjM1qXY2E3mHv0uqKk
=P8W4
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Thu Mar 12 10:51:15 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 12 Mar 2015 10:51:15 +0000
Subject: [Pkg-puppet-devel] Bug#774643: marked as done (Lacking support of
	exported resources)
References: <E1YW0fo-0007as-Lj@franck.debian.org>
 <20150105173833.GA14180@localhost>
Message-ID: <handler.774643.D774643.142615734620799.ackdone@bugs.debian.org>

Your message dated Thu, 12 Mar 2015 10:49:04 +0000
with message-id <E1YW0fo-0007as-Lj at franck.debian.org>
and subject line Bug#774643: fixed in puppet 3.7.2-3
has caused the Debian Bug report #774643,
regarding Lacking support of exported resources
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
774643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774643
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: bertagaz <bertagaz at ptitcanardnoir.org>
Subject: Lacking support of exported resources
Date: Mon, 5 Jan 2015 18:38:33 +0100
Size: 2682
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/e4b521ed/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Apollon Oikonomopoulos <apoikos at debian.org>
Subject: Bug#774643: fixed in puppet 3.7.2-3
Date: Thu, 12 Mar 2015 10:49:04 +0000
Size: 8235
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/e4b521ed/attachment-0003.mht>

From owner at bugs.debian.org  Thu Mar 12 10:51:20 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 12 Mar 2015 10:51:20 +0000
Subject: [Pkg-puppet-devel] Bug#775795: marked as done (puppet: Service's
 debian provider assumes SysV init)
References: <E1YW0fo-0007ay-Md@franck.debian.org>
 <20150120023502.GA13121@dewey.void.home>
Message-ID: <handler.775795.D775795.142615734620811.ackdone@bugs.debian.org>

Your message dated Thu, 12 Mar 2015 10:49:04 +0000
with message-id <E1YW0fo-0007ay-Md at franck.debian.org>
and subject line Bug#775795: fixed in puppet 3.7.2-3
has caused the Debian Bug report #775795,
regarding puppet: Service's debian provider assumes SysV init
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
775795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Faidon Liambotis <paravoid at debian.org>
Subject: puppet: Service's debian provider assumes SysV init
Date: Mon, 19 Jan 2015 18:35:09 -0800
Size: 4653
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/1dd43943/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Apollon Oikonomopoulos <apoikos at debian.org>
Subject: Bug#775795: fixed in puppet 3.7.2-3
Date: Thu, 12 Mar 2015 10:49:04 +0000
Size: 8260
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/1dd43943/attachment-0001.mht>

From owner at bugs.debian.org  Thu Mar 12 10:51:24 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 12 Mar 2015 10:51:24 +0000
Subject: [Pkg-puppet-devel] Bug#778891: marked as done (puppet: systemd unit
 file does not load environment from /etc/default/puppet - breaks upgrades)
References: <E1YW0fo-0007b4-NX@franck.debian.org>
 <20150221112556.3018.54594.reportbug@mercury.esat.kuleuven.be>
Message-ID: <handler.778891.D778891.142615734620824.ackdone@bugs.debian.org>

Your message dated Thu, 12 Mar 2015 10:49:04 +0000
with message-id <E1YW0fo-0007b4-NX at franck.debian.org>
and subject line Bug#778891: fixed in puppet 3.7.2-3
has caused the Debian Bug report #778891,
regarding puppet: systemd unit file does not load environment from /etc/default/puppet - breaks upgrades
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
778891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778891
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Rik Theys <Rik.Theys at esat.kuleuven.be>
Subject: puppet: systemd unit file does not load environment from /etc/default/puppet - breaks upgrades
Date: Sat, 21 Feb 2015 12:25:56 +0100
Size: 6446
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/e0f26c0d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Apollon Oikonomopoulos <apoikos at debian.org>
Subject: Bug#778891: fixed in puppet 3.7.2-3
Date: Thu, 12 Mar 2015 10:49:04 +0000
Size: 8258
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150312/e0f26c0d/attachment-0003.mht>

From apoikos at debian.org  Thu Mar 12 10:59:44 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Thu, 12 Mar 2015 12:59:44 +0200
Subject: [Pkg-puppet-devel] Bug#780223: unblock: puppet/3.7.2-3
In-Reply-To: <5500A6FF.8050100@thykier.net>
References: <20150310185914.GA9993@marvin.ws.skroutz.gr>
 <5500A6FF.8050100@thykier.net>
Message-ID: <20150312105944.GA27211@marvin.ws.skroutz.gr>

Control: tags -1 - moreinfo

Hi,

On 21:35 Wed 11 Mar     , Niels Thykier wrote:
> Ack, looks good.  Please upload it to unstable and remove the moreinfo
> tag once it has been accepted.

Uploaded and accepted into unstable with the following minor changes:

 - Add a note in README.Debian clarifying the dependencies needed for 
   stored configs to work and noting the deprecation status.

 - Improve the ActiveRecord 4 patch to also include 
   clear_active_connections! stubs in the testsuite's specs. We do not 
   use the test suite directly, but are shipping it in puppet-testsuite, 
   so I did the change for completeness.

Full debdiff since 3.7.2-2 and interdiff attached.

Regards,
Apollon
-------------- next part --------------
diff -u puppet-3.7.2/debian/changelog puppet-3.7.2/debian/changelog
--- puppet-3.7.2/debian/changelog	2015-03-10 19:57:24.000000000 +0200
+++ puppet-3.7.2/debian/changelog	2015-03-12 11:46:11.000000000 +0200
@@ -5,6 +5,8 @@
   * Fix service enable/disable in the Debian service provider (Closes: #775795)
   * Fix stored configs with ActiveRecord 4.x (Closes: #774643)
     + puppetmaster-common: add Recommends for stored configs
+    + Mention stored configs dependencies in README.Debian. Also add a
+      note for the deprecation of AR-based stored configs.
   * Preserve and honor changes in /etc/default/puppet (Closes: #778891)
     + Do not remove /etc/default/puppet on upgrade
     + Disable the agent when upgrading and START != yes
diff -u puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch
--- puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	2015-03-10 19:57:24.000000000 +0200
+++ puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	2015-03-12 11:46:11.000000000 +0200
@@ -1,6 +1,6 @@
-From 988b0aff88429f820ee247533b8aed4a77d11a62 Mon Sep 17 00:00:00 2001
+From 5628459ba86a5d535babd6e904de9db42045d6d4 Mon Sep 17 00:00:00 2001
 From: Apollon Oikonomopoulos <apoikos at debian.org>
-Date: Tue, 10 Mar 2015 19:46:39 +0200
+Date: Thu, 12 Mar 2015 11:33:05 +0200
 Subject: Stored configs compatibility with ActiveRecord 4.x
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
@@ -30,7 +30,8 @@
  lib/puppet/rails/fact_value.rb      |  3 +++
  lib/puppet/rails/param_value.rb     |  4 ++--
  lib/puppet/rails/resource_tag.rb    |  4 ++--
- 6 files changed, 24 insertions(+), 15 deletions(-)
+ spec/unit/rails_spec.rb             |  6 +++---
+ 7 files changed, 27 insertions(+), 18 deletions(-)
 
 diff --git a/lib/puppet/rails.rb b/lib/puppet/rails.rb
 index 2c97c02..adb20fb 100644
@@ -189,6 +190,30 @@
      tags.each do |val|
        val['resource_id'] = Integer(val['resource_id'])
      end
+diff --git a/spec/unit/rails_spec.rb b/spec/unit/rails_spec.rb
+index b12f81f..2fb0e4f 100755
+--- a/spec/unit/rails_spec.rb
++++ b/spec/unit/rails_spec.rb
+@@ -37,7 +37,7 @@ describe Puppet::Rails, "when initializing any connection", :if => Puppet.featur
+     logger.expects(:level=).with(Logger::DEBUG)
+ 
+     ActiveRecord::Base.stubs(:allow_concurrency=)
+-    ActiveRecord::Base.stubs(:verify_active_connections!)
++    ActiveRecord::Base.stubs(:clear_active_connections!)
+     ActiveRecord::Base.stubs(:establish_connection)
+     Puppet::Rails.stubs(:database_arguments).returns({})
+ 
+@@ -60,8 +60,8 @@ describe Puppet::Rails, "when initializing any connection", :if => Puppet.featur
+     end
+   end
+ 
+-  it "should call ActiveRecord::Base.verify_active_connections!" do
+-    ActiveRecord::Base.expects(:verify_active_connections!)
++  it "should call ActiveRecord::Base.clear_active_connections!" do
++    ActiveRecord::Base.expects(:clear_active_connections!)
+ 
+     Puppet::Rails.connect
+   end
 -- 
 2.1.4
 
only in patch2:
unchanged:
--- puppet-3.7.2/debian/README.Debian	2014-11-13 13:56:19.000000000 +0200
+++ puppet-3.7.2/debian/README.Debian	2015-03-12 11:45:42.000000000 +0200
@@ -10,3 +10,17 @@
 changes made to files in /etc via etckeeper before and after its run.
 
  -- Stig Sandbeck Mathisen <ssm at debian.org>, Mon,  5 Aug 2013 23:36:19 +0200
+
+Using stored configs
+--------------------
+
+Using the master's stored configs functionality with the ActiveRecord backend
+requires the ruby-activerecord (and, since Jessie,
+ruby-activerecord-deprecated-finders) packages to be installed. Furthermore a
+database adapter for the database of choice (e.g. ruby-mysql) must be
+installed.
+
+Note that ActiveRecord-based stored configs are deprecated and will be removed
+in Puppet 4 in favor of PuppetDB.
+
+ -- Apollon Oikonomopulos <apoikos at debian.org>  Thu, 12 Mar 2015 10:50:47 +0200
-------------- next part --------------
diff -Nru puppet-3.7.2/debian/changelog puppet-3.7.2/debian/changelog
--- puppet-3.7.2/debian/changelog	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/changelog	2015-03-12 11:46:11.000000000 +0200
@@ -1,3 +1,23 @@
+puppet (3.7.2-3) unstable; urgency=medium
+
+  [ Apollon Oikonomopoulos ]
+  * Team upload.
+  * Fix service enable/disable in the Debian service provider (Closes: #775795)
+  * Fix stored configs with ActiveRecord 4.x (Closes: #774643)
+    + puppetmaster-common: add Recommends for stored configs
+    + Mention stored configs dependencies in README.Debian. Also add a
+      note for the deprecation of AR-based stored configs.
+  * Preserve and honor changes in /etc/default/puppet (Closes: #778891)
+    + Do not remove /etc/default/puppet on upgrade
+    + Disable the agent when upgrading and START != yes
+    + puppet.service: pass $DAEMON_OPTS to puppet agent. Thanks to Rik Theys!
+    + Add a NEWS note about the START flag
+
+  [ Stig Sandbeck Mathisen ]
+  * Add upstream metadata
+
+ -- Apollon Oikonomopoulos <apoikos at debian.org>  Tue, 10 Mar 2015 14:33:45 +0200
+
 puppet (3.7.2-2) unstable; urgency=medium
 
   [ Gaudenz Steinlin ]
diff -Nru puppet-3.7.2/debian/control puppet-3.7.2/debian/control
--- puppet-3.7.2/debian/control	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/control	2015-03-10 19:57:24.000000000 +0200
@@ -81,6 +81,8 @@
  ruby | ruby-interpreter,
 Breaks: puppet (<< 0.24.7-1), puppetmaster (<< 2.7.6-1~)
 Replaces: puppet (<< 0.24.7-1), puppetmaster (<< 2.7.6-1~)
+Recommends: ruby-activerecord,
+ ruby-activerecord-deprecated-finders
 Suggests:
  apache2 | nginx,
  puppet-el,
diff -Nru puppet-3.7.2/debian/copyright puppet-3.7.2/debian/copyright
--- puppet-3.7.2/debian/copyright	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/copyright	2015-03-10 16:11:08.000000000 +0200
@@ -1,6 +1,6 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: Puppet
-Source: git://github.com/reductivelabs/puppet.git,
+Source: https://github.com/puppetlabs/puppet
 
 Files: *
 Copyright: 2004-2012 Puppet Labs Inc
diff -Nru puppet-3.7.2/debian/NEWS puppet-3.7.2/debian/NEWS
--- puppet-3.7.2/debian/NEWS	2014-11-13 13:56:19.000000000 +0200
+++ puppet-3.7.2/debian/NEWS	2015-03-10 19:57:24.000000000 +0200
@@ -1,3 +1,17 @@
+puppet (3.7.2-3) unstable; urgency=medium
+ 
+  The START flag in /etc/default/puppet is since 3.2.4-1 no longer effective.
+  To preserve state across upgrades for old setups where the puppet agent was
+  disabled using the START flag, the agent will be disabled using its built-in
+  disable facility if START is not set to true. In that case, you will need to
+  run "puppet agent --enable" before the agent can connect to a puppet master.
+
+  On systems running the puppet agent via cron, make sure that you do not rely
+  on the START variable in /etc/default/puppet and instead disable the
+  service using update-rc.d or systemctl.
+
+ -- Apollon Oikonomopoulos <apoikos at debian.org>  Tue, 10 Mar 2015 14:54:15 +0200
+
 puppet (3.2.4-1) unstable; urgency=high
 
   The puppet agent is now started by default, regardless of init system.
diff -Nru puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch
--- puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/patches/0005-Fix-service-listing-and-enable-disable-in-Debian.patch	2015-03-10 16:11:08.000000000 +0200
@@ -0,0 +1,161 @@
+From a9b76dbfba96f537227c445297d3ccd115de46ca Mon Sep 17 00:00:00 2001
+From: Apollon Oikonomopoulos <apoikos at debian.org>
+Date: Fri, 27 Feb 2015 10:55:34 +0200
+Subject: [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/provider/service/debian.rb | 94 ++++++++++++++++++++++++++---------
+ 1 file changed, 71 insertions(+), 23 deletions(-)
+
+diff --git a/lib/puppet/provider/service/debian.rb b/lib/puppet/provider/service/debian.rb
+index 9f7a2f5..7a26409 100644
+--- a/lib/puppet/provider/service/debian.rb
++++ b/lib/puppet/provider/service/debian.rb
+@@ -15,6 +15,7 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+   # http://projects.reductivelabs.com/issues/2538
+   # is resolved.
+   commands :invoke_rc => "/usr/sbin/invoke-rc.d"
++  optional_commands :systemctl => "/bin/systemctl"
+ 
+   # This isn't being used directly, it's just here to ensure
+   # that the /usr/sbin/service binary is available.
+@@ -23,38 +24,82 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+ 
+   defaultfor :operatingsystem => :debian
+ 
++  def self.runs_on_systemd?
++    Dir.exists? "/run/systemd/system"
++  end
++
++  def is_sysv_unit?
++    # The sysv generator sets the SourcePath attribute to the name of the
++    # initscript. Use this to detect whether a unit is backed by an initscript
++    # or not.
++    source = systemctl(:show, "-pSourcePath", @resource[:name])
++    source.start_with? "SourcePath=/etc/init.d/"
++  end
++
++  def self.instances
++    # We need to merge services with systemd unit files with those only having
++    # an initscript. Note that we could use `systemctl --all` to get sysv
++    # services as well, however it would only output *enabled* services.
++    i = {}
++    if self.runs_on_systemd?
++      begin
++        output = systemctl('list-unit-files', '--type', 'service', '--full', '--all',  '--no-pager')
++        output.scan(/^(\S+)\.service\s+(disabled|enabled)\s*$/i).each do |m|
++          i[m[0]] = new(:name => m[0])
++        end
++      rescue Puppet::ExecutionFailure
++      end
++    end
++    get_services(defpath).each do |sysv|
++      unless i.has_key?(sysv.name)
++        i[sysv.name] = sysv
++      end
++    end
++    return i.values
++  end
++
+   # Remove the symlinks
+   def disable
+-    if `dpkg --compare-versions $(dpkg-query -W --showformat '${Version}' sysv-rc) ge 2.88 ; echo $?`.to_i == 0
+-      update_rc @resource[:name], "disable"
++    if self.class.runs_on_systemd?
++      systemctl(:disable, @resource[:name])
+     else
+-      update_rc "-f", @resource[:name], "remove"
+-      update_rc @resource[:name], "stop", "00", "1", "2", "3", "4", "5", "6", "."
++      update_rc @resource[:name], "disable"
+     end
+   end
+ 
+   def enabled?
+-    # TODO: Replace system call when Puppet::Util::Execution.execute gives us a way
+-    # to determine exit status.  http://projects.reductivelabs.com/issues/2538
+-    system("/usr/sbin/invoke-rc.d", "--quiet", "--query", @resource[:name], "start")
+-
+-    # 104 is the exit status when you query start an enabled service.
+-    # 106 is the exit status when the policy layer supplies a fallback action
+-    # See x-man-page://invoke-rc.d
+-    if [104, 106].include?($CHILD_STATUS.exitstatus)
+-      return :true
+-    elsif [105].include?($CHILD_STATUS.exitstatus)
+-      # 105 is unknown, which generally means the iniscript does not support query
+-      # The debian policy states that the initscript should support methods of query
+-      # For those that do not, peform the checks manually
+-      # http://www.debian.org/doc/debian-policy/ch-opersys.html
+-      if get_start_link_count >= 4
++    # Initscript-backed services have no enabled status in systemd, so we
++    # need to query them using invoke-rc.d.
++    if self.class.runs_on_systemd? and not is_sysv_unit?
++      begin
++        systemctl("is-enabled", @resource[:name])
+         return :true
+-      else
++      rescue Puppet::ExecutionFailure
+         return :false
+       end
+     else
+-      return :false
++      # TODO: Replace system call when Puppet::Util::Execution.execute gives us a way
++      # to determine exit status.  http://projects.reductivelabs.com/issues/2538
++      system("/usr/sbin/invoke-rc.d", "--quiet", "--query", @resource[:name], "start")
++
++      # 104 is the exit status when you query start an enabled service.
++      # 106 is the exit status when the policy layer supplies a fallback action
++      # See x-man-page://invoke-rc.d
++      if [104, 106].include?($CHILD_STATUS.exitstatus)
++        return :true
++      elsif [105].include?($CHILD_STATUS.exitstatus)
++        # 105 is unknown, which generally means the iniscript does not support query
++        # The debian policy states that the initscript should support methods of query
++        # For those that do not, peform the checks manually
++        # http://www.debian.org/doc/debian-policy/ch-opersys.html
++        if get_start_link_count >= 4
++          return :true
++        else
++          return :false
++        end
++      else
++        return :false
++      end
+     end
+   end
+ 
+@@ -63,8 +108,11 @@ Puppet::Type.type(:service).provide :debian, :parent => :init do
+   end
+ 
+   def enable
+-    update_rc "-f", @resource[:name], "remove"
+-    update_rc @resource[:name], "defaults"
++    if self.class.runs_on_systemd?
++      systemctl(:enable, @resource[:name])
++    else
++      update_rc @resource[:name], "enable"
++    end
+   end
+ 
+   # The start, stop, restart and status command use service
+-- 
+2.1.4
+
diff -Nru puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch
--- puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/patches/0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch	2015-03-12 11:46:11.000000000 +0200
@@ -0,0 +1,219 @@
+From 5628459ba86a5d535babd6e904de9db42045d6d4 Mon Sep 17 00:00:00 2001
+From: Apollon Oikonomopoulos <apoikos at debian.org>
+Date: Thu, 12 Mar 2015 11:33:05 +0200
+Subject: 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/rails.rb                 |  5 ++++-
+ lib/puppet/rails/database/schema.rb | 20 ++++++++++----------
+ lib/puppet/rails/fact_name.rb       |  3 +++
+ lib/puppet/rails/fact_value.rb      |  3 +++
+ lib/puppet/rails/param_value.rb     |  4 ++--
+ lib/puppet/rails/resource_tag.rb    |  4 ++--
+ spec/unit/rails_spec.rb             |  6 +++---
+ 7 files changed, 27 insertions(+), 18 deletions(-)
+
+diff --git a/lib/puppet/rails.rb b/lib/puppet/rails.rb
+index 2c97c02..adb20fb 100644
+--- a/lib/puppet/rails.rb
++++ b/lib/puppet/rails.rb
+@@ -8,6 +8,9 @@ module Puppet::Rails
+   TIME_DEBUG = true
+ 
+   def self.connect
++    # Silence activerecord deprecation warnings
++    ActiveSupport::Deprecation.silenced = true
++
+     # This global init does not work for testing, because we remove
+     # the state dir on every test.
+     return if ActiveRecord::Base.connected?
+@@ -26,7 +29,7 @@ module Puppet::Rails
+     # As of ActiveRecord 2.2 allow_concurrency has been deprecated and no longer has any effect.
+     ActiveRecord::Base.allow_concurrency = true if Puppet::Util.activerecord_version < 2.2
+ 
+-    ActiveRecord::Base.verify_active_connections!
++    ActiveRecord::Base.clear_active_connections!
+ 
+     begin
+       args = database_arguments
+diff --git a/lib/puppet/rails/database/schema.rb b/lib/puppet/rails/database/schema.rb
+index 931a1b6..1216719 100644
+--- a/lib/puppet/rails/database/schema.rb
++++ b/lib/puppet/rails/database/schema.rb
+@@ -19,8 +19,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :resources, :host_id, :integer => true
+-        add_index :resources, :source_file_id, :integer => true
++        add_index :resources, :host_id
++        add_index :resources, :source_file_id
+ 
+         # Thanks, mysql!  MySQL requires a length on indexes in text fields.
+         # So, we provide them for mysql and handle everything else specially.
+@@ -45,8 +45,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :resource_tags, :resource_id, :integer => true
+-        add_index :resource_tags, :puppet_tag_id, :integer => true
++        add_index :resource_tags, :resource_id
++        add_index :resource_tags, :puppet_tag_id
+ 
+         create_table :puppet_tags do |t|
+           t.column :name, :string
+@@ -55,7 +55,7 @@ class Puppet::Rails::Schema
+         end
+ 
+         # Oracle automatically creates a primary key index
+-        add_index :puppet_tags, :id, :integer => true if Puppet[:dbadapter] != "oracle_enhanced"
++        add_index :puppet_tags, :id if Puppet[:dbadapter] != "oracle_enhanced"
+ 
+         create_table :hosts do |t|
+           t.column :name, :string, :null => false
+@@ -69,7 +69,7 @@ class Puppet::Rails::Schema
+           t.column :source_file_id, :integer
+           t.column :created_at, :datetime
+         end
+-        add_index :hosts, :source_file_id, :integer => true
++        add_index :hosts, :source_file_id
+         add_index :hosts, :name
+ 
+         create_table :fact_names do |t|
+@@ -86,8 +86,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :fact_values, :fact_name_id, :integer => true
+-        add_index :fact_values, :host_id, :integer => true
++        add_index :fact_values, :fact_name_id
++        add_index :fact_values, :host_id
+ 
+         create_table :param_values do |t|
+           t.column :value,  :text, :null => false
+@@ -97,8 +97,8 @@ class Puppet::Rails::Schema
+           t.column :updated_at, :datetime
+           t.column :created_at, :datetime
+         end
+-        add_index :param_values, :param_name_id, :integer => true
+-        add_index :param_values, :resource_id, :integer => true
++        add_index :param_values, :param_name_id
++        add_index :param_values, :resource_id
+ 
+         create_table :param_names do |t|
+           t.column :name, :string, :null => false
+diff --git a/lib/puppet/rails/fact_name.rb b/lib/puppet/rails/fact_name.rb
+index 073bbcb..5fe5264 100644
+--- a/lib/puppet/rails/fact_name.rb
++++ b/lib/puppet/rails/fact_name.rb
+@@ -1,4 +1,7 @@
+ require 'active_record'
++if Gem::Version.new(ActiveRecord::VERSION::STRING) >= Gem::Version.new('4.1')
++  require 'active_record/deprecated_finders'
++end
+ require 'puppet/rails'
+ require 'puppet/rails/fact_value'
+ 
+diff --git a/lib/puppet/rails/fact_value.rb b/lib/puppet/rails/fact_value.rb
+index 918c0ac..d1657b9 100644
+--- a/lib/puppet/rails/fact_value.rb
++++ b/lib/puppet/rails/fact_value.rb
+@@ -1,4 +1,7 @@
+ require 'active_record'
++if Gem::Version.new(ActiveRecord::VERSION::STRING) >= Gem::Version.new('4.1')
++  require 'active_record/deprecated_finders'
++end
+ 
+ class Puppet::Rails::FactValue < ActiveRecord::Base
+   belongs_to :fact_name
+diff --git a/lib/puppet/rails/param_value.rb b/lib/puppet/rails/param_value.rb
+index d7c88f8..e082ed8 100644
+--- a/lib/puppet/rails/param_value.rb
++++ b/lib/puppet/rails/param_value.rb
+@@ -48,7 +48,7 @@ class Puppet::Rails::ParamValue < ActiveRecord::Base
+ 
+   # returns an array of hash containing all the parameters of a given resource
+   def self.find_all_params_from_resource(db_resource)
+-    params = db_resource.connection.select_all("SELECT v.id, v.value, v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN param_names n ON v.param_name_id=n.id WHERE v.resource_id=#{db_resource.id}")
++    params = ActiveRecord::Base.connection.select_all("SELECT v.id, v.value, v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN param_names n ON v.param_name_id=n.id WHERE v.resource_id=#{db_resource.id}")
+     params.each do |val|
+       val['value'] = unserialize_value(val['value'])
+       val['line'] = val['line'] ? Integer(val['line']) : nil
+@@ -59,7 +59,7 @@ class Puppet::Rails::ParamValue < ActiveRecord::Base
+ 
+   # returns an array of hash containing all the parameters of a given host
+   def self.find_all_params_from_host(db_host)
+-    params = db_host.connection.select_all("SELECT v.id, v.value,  v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN resources r ON v.resource_id=r.id INNER JOIN param_names n ON v.param_name_id=n.id WHERE r.host_id=#{db_host.id}")
++    params = ActiveRecord::Base.connection.select_all("SELECT v.id, v.value,  v.line, v.resource_id, v.param_name_id, n.name FROM param_values v INNER JOIN resources r ON v.resource_id=r.id INNER JOIN param_names n ON v.param_name_id=n.id WHERE r.host_id=#{db_host.id}")
+     params.each do |val|
+       val['value'] = unserialize_value(val['value'])
+       val['line'] = val['line'] ? Integer(val['line']) : nil
+diff --git a/lib/puppet/rails/resource_tag.rb b/lib/puppet/rails/resource_tag.rb
+index 1c1aa45..1493d3e 100644
+--- a/lib/puppet/rails/resource_tag.rb
++++ b/lib/puppet/rails/resource_tag.rb
+@@ -8,7 +8,7 @@ class Puppet::Rails::ResourceTag < ActiveRecord::Base
+ 
+   # returns an array of hash containing tags of resource
+   def self.find_all_tags_from_resource(db_resource)
+-    tags = db_resource.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE t.resource_id=#{db_resource.id}")
++    tags = ActiveRecord::Base.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE t.resource_id=#{db_resource.id}")
+     tags.each do |val|
+       val['resource_id'] = Integer(val['resource_id'])
+     end
+@@ -17,7 +17,7 @@ class Puppet::Rails::ResourceTag < ActiveRecord::Base
+ 
+   # returns an array of hash containing tags of a host
+   def self.find_all_tags_from_host(db_host)
+-    tags = db_host.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN resources r ON t.resource_id=r.id INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE r.host_id=#{db_host.id}")
++    tags = ActiveRecord::Base.connection.select_all("SELECT t.id, t.resource_id, p.name FROM resource_tags t INNER JOIN resources r ON t.resource_id=r.id INNER JOIN puppet_tags p ON t.puppet_tag_id=p.id WHERE r.host_id=#{db_host.id}")
+     tags.each do |val|
+       val['resource_id'] = Integer(val['resource_id'])
+     end
+diff --git a/spec/unit/rails_spec.rb b/spec/unit/rails_spec.rb
+index b12f81f..2fb0e4f 100755
+--- a/spec/unit/rails_spec.rb
++++ b/spec/unit/rails_spec.rb
+@@ -37,7 +37,7 @@ describe Puppet::Rails, "when initializing any connection", :if => Puppet.featur
+     logger.expects(:level=).with(Logger::DEBUG)
+ 
+     ActiveRecord::Base.stubs(:allow_concurrency=)
+-    ActiveRecord::Base.stubs(:verify_active_connections!)
++    ActiveRecord::Base.stubs(:clear_active_connections!)
+     ActiveRecord::Base.stubs(:establish_connection)
+     Puppet::Rails.stubs(:database_arguments).returns({})
+ 
+@@ -60,8 +60,8 @@ describe Puppet::Rails, "when initializing any connection", :if => Puppet.featur
+     end
+   end
+ 
+-  it "should call ActiveRecord::Base.verify_active_connections!" do
+-    ActiveRecord::Base.expects(:verify_active_connections!)
++  it "should call ActiveRecord::Base.clear_active_connections!" do
++    ActiveRecord::Base.expects(:clear_active_connections!)
+ 
+     Puppet::Rails.connect
+   end
+-- 
+2.1.4
+
diff -Nru puppet-3.7.2/debian/patches/series puppet-3.7.2/debian/patches/series
--- puppet-3.7.2/debian/patches/series	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/patches/series	2015-03-10 16:11:08.000000000 +0200
@@ -2,3 +2,5 @@
 0002-Set-passenger-puppet-master-document-root.patch
 0003-fix-puppet-master-logcheck-rule.patch
 0004-debian-service-provider-use-service.patch
+0005-Fix-service-listing-and-enable-disable-in-Debian.patch
+0006-Storeconfigs-compatibility-with-ActiveRecord-4.patch
diff -Nru puppet-3.7.2/debian/puppet-common.preinst puppet-3.7.2/debian/puppet-common.preinst
--- puppet-3.7.2/debian/puppet-common.preinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet-common.preinst	2015-03-10 19:57:24.000000000 +0200
@@ -18,7 +18,7 @@
     tmp_lockfile=$(mktemp /var/lib/puppet/state/agent_disabled.lock.XXXXXXXX)
     lockfile=/var/lib/puppet/state/agent_disabled.lock
 
-    printf '{"disabled_message":"Disabled by default on new installations"}' \
+    printf '{"disabled_message":"Disabled by default on new or unconfigured old installations"}' \
         > $tmp_lockfile
 
     mv $tmp_lockfile $lockfile
@@ -29,10 +29,33 @@
         # disable the puppet agent on the first install
         if [ -z "$2" ]; then
             disable_puppet_agent
+        elif dpkg --compare-versions "$2" lt "3.2.4-1~" && \
+            [ -e "/etc/default/puppet" ]; then
+            # Also disable puppet if we use conffiles from a version where the
+            # START flag mattered.
+            . /etc/default/puppet
+
+            if [ "x$START" != "xtrue" -a "x$START" != "xyes" -a "x$START" != "x0" ]; then
+                # Note that "0" is not a typo, it reflects the checks done
+                # in wheezy's initscript.
+                disable_puppet_agent
+            fi
         fi
         ;;
 
     upgrade)
+        # Disable puppet if we are upgrading from a version where the START
+        # flag mattered.
+        if dpkg --compare-versions "$2" lt "3.2.4-1~" && \
+            [ -e "/etc/default/puppet" ]; then
+            . /etc/default/puppet
+
+            if [ "x$START" != "xtrue" -a "x$START" != "xyes" -a "x$START" != "x0" ]; then
+                # Note that "0" is not a typo, it reflects the checks done
+                # in wheezy's initscript.
+                disable_puppet_agent
+            fi
+        fi
         ;;
 
     abort-upgrade)
diff -Nru puppet-3.7.2/debian/puppet.postinst puppet-3.7.2/debian/puppet.postinst
--- puppet-3.7.2/debian/puppet.postinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.postinst	1970-01-01 02:00:00.000000000 +0200
@@ -1,44 +0,0 @@
-#!/bin/sh
-# postinst script for puppet
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <postinst> `configure' <most-recently-configured-version>
-#        * <old-postinst> `abort-upgrade' <new version>
-#        * <conflictor's-postinst> `abort-remove' `in-favour' <package>
-#          <new-version>
-#        * <postinst> `abort-remove'
-#        * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-#          <failed-install-package> <version> `removing'
-#          <conflicting-package> <version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    configure)
-    ;;
-
-    abort-upgrade|abort-remove|abort-deconfigure)
-    ;;
-
-    *)
-        echo "postinst called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-if dpkg-maintscript-helper supports rm_conffile; then
-    dpkg-maintscript-helper rm_conffile \
-        /etc/default/puppet 3.2.3-1 puppet -- "$@"
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.postrm puppet-3.7.2/debian/puppet.postrm
--- puppet-3.7.2/debian/puppet.postrm	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.postrm	1970-01-01 02:00:00.000000000 +0200
@@ -1,42 +0,0 @@
-#!/bin/sh
-# postrm script for puppet
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <postrm> `remove'
-#        * <postrm> `purge'
-#        * <old-postrm> `upgrade' <new-version>
-#        * <new-postrm> `failed-upgrade' <old-version>
-#        * <new-postrm> `abort-install'
-#        * <new-postrm> `abort-install' <old-version>
-#        * <new-postrm> `abort-upgrade' <old-version>
-#        * <disappearer's-postrm> `disappear' <overwriter>
-#          <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
-        if dpkg-maintscript-helper supports rm_conffile; then
-            dpkg-maintscript-helper rm_conffile \
-                /etc/default/puppet 3.2.3-1 puppet -- "$@"
-        fi
-
-    ;;
-
-    *)
-        echo "postrm called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.preinst puppet-3.7.2/debian/puppet.preinst
--- puppet-3.7.2/debian/puppet.preinst	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.preinst	1970-01-01 02:00:00.000000000 +0200
@@ -1,40 +0,0 @@
-#!/bin/sh
-# preinst script for #PACKAGE#
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <new-preinst> `install'
-#        * <new-preinst> `install' <old-version>
-#        * <new-preinst> `upgrade' <old-version>
-#        * <old-preinst> `abort-upgrade' <new-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    install|upgrade)
-    ;;
-
-    abort-upgrade)
-    ;;
-
-    *)
-        echo "preinst called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-if dpkg-maintscript-helper supports rm_conffile; then
-    dpkg-maintscript-helper rm_conffile \
-        /etc/default/puppet 3.2.3-1 puppet -- "$@"
-fi
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
diff -Nru puppet-3.7.2/debian/puppet.service puppet-3.7.2/debian/puppet.service
--- puppet-3.7.2/debian/puppet.service	2015-03-10 14:41:11.000000000 +0200
+++ puppet-3.7.2/debian/puppet.service	2015-03-10 19:57:24.000000000 +0200
@@ -3,8 +3,9 @@
 
 [Service]
 Type=forking
+EnvironmentFile=-/etc/default/puppet
 PIDFile=/run/puppet/agent.pid
-ExecStart=/usr/bin/puppet agent
+ExecStart=/usr/bin/puppet agent $DAEMON_OPTS
 
 [Install]
 WantedBy=multi-user.target
diff -Nru puppet-3.7.2/debian/README.Debian puppet-3.7.2/debian/README.Debian
--- puppet-3.7.2/debian/README.Debian	2014-11-13 13:56:19.000000000 +0200
+++ puppet-3.7.2/debian/README.Debian	2015-03-12 11:45:42.000000000 +0200
@@ -10,3 +10,17 @@
 changes made to files in /etc via etckeeper before and after its run.
 
  -- Stig Sandbeck Mathisen <ssm at debian.org>, Mon,  5 Aug 2013 23:36:19 +0200
+
+Using stored configs
+--------------------
+
+Using the master's stored configs functionality with the ActiveRecord backend
+requires the ruby-activerecord (and, since Jessie,
+ruby-activerecord-deprecated-finders) packages to be installed. Furthermore a
+database adapter for the database of choice (e.g. ruby-mysql) must be
+installed.
+
+Note that ActiveRecord-based stored configs are deprecated and will be removed
+in Puppet 4 in favor of PuppetDB.
+
+ -- Apollon Oikonomopulos <apoikos at debian.org>  Thu, 12 Mar 2015 10:50:47 +0200
diff -Nru puppet-3.7.2/debian/upstream/metadata puppet-3.7.2/debian/upstream/metadata
--- puppet-3.7.2/debian/upstream/metadata	1970-01-01 02:00:00.000000000 +0200
+++ puppet-3.7.2/debian/upstream/metadata	2015-03-10 16:11:08.000000000 +0200
@@ -0,0 +1,4 @@
+---
+Bug-Database: https://tickets.puppetlabs.com/browse/PUP
+Repository: https://github.com/puppetlabs/puppet.git
+Repository-Browse: https://github.com/puppetlabs/puppet

From niels at thykier.net  Thu Mar 12 16:34:08 2015
From: niels at thykier.net (Niels Thykier)
Date: Thu, 12 Mar 2015 17:34:08 +0100
Subject: [Pkg-puppet-devel] Bug#780223: unblock: puppet/3.7.2-3
In-Reply-To: <20150312105944.GA27211@marvin.ws.skroutz.gr>
References: <20150310185914.GA9993@marvin.ws.skroutz.gr>
 <5500A6FF.8050100@thykier.net> <20150312105944.GA27211@marvin.ws.skroutz.gr>
Message-ID: <5501C000.4070704@thykier.net>

On 2015-03-12 11:59, Apollon Oikonomopoulos wrote:
> Control: tags -1 - moreinfo
> 
> Hi,
> 
> On 21:35 Wed 11 Mar     , Niels Thykier wrote:
>> Ack, looks good.  Please upload it to unstable and remove the moreinfo
>> tag once it has been accepted.
> 
> Uploaded and accepted into unstable with the following minor changes:
> 
>  - Add a note in README.Debian clarifying the dependencies needed for 
>    stored configs to work and noting the deprecation status.
> 
>  - Improve the ActiveRecord 4 patch to also include 
>    clear_active_connections! stubs in the testsuite's specs. We do not 
>    use the test suite directly, but are shipping it in puppet-testsuite, 
>    so I did the change for completeness.
> 
> Full debdiff since 3.7.2-2 and interdiff attached.
> 
> Regards,
> Apollon
> 

Unblocked, thanks.

~Niels




From bts-link-upstream at lists.alioth.debian.org  Thu Mar 12 17:14:32 2015
From: bts-link-upstream at lists.alioth.debian.org (bts-link-upstream at lists.alioth.debian.org)
Date: Thu, 12 Mar 2015 17:14:32 -0000
Subject: [Pkg-puppet-devel] [bts-link] source package puppet
Message-ID: <20150312171422.28522.8883.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package puppet
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user bts-link-upstream at lists.alioth.debian.org

# remote status report for #769621 (http://bugs.debian.org/769621)
# Bug title: puppet: USR1 fails to trigger agent run
#  * https://tickets.puppetlabs.com/browse/PUP-1635
#  * remote status changed: Ready-for-Test -> Resolved
#  * remote resolution changed: (?) -> Fixed
#  * closed upstream
tags 769621 + fixed-upstream
usertags 769621 - status-Ready-for-Test
usertags 769621 + status-Resolved resolution-Fixed

thanks


From owner at bugs.debian.org  Thu Mar 12 17:15:44 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 12 Mar 2015 17:15:44 +0000
Subject: [Pkg-puppet-devel] Processed: [bts-link] source package puppet
References: <20150312171422.28522.8883.btslink@sonntag.debian.org>
Message-ID: <handler.s.C.14261804698634.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> #
> # bts-link upstream status pull for source package puppet
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user bts-link-upstream at lists.alioth.debian.org
Setting user to bts-link-upstream at lists.alioth.debian.org (was bts-link-devel at lists.alioth.debian.org).
> # remote status report for #769621 (http://bugs.debian.org/769621)
> # Bug title: puppet: USR1 fails to trigger agent run
> #  * https://tickets.puppetlabs.com/browse/PUP-1635
> #  * remote status changed: Ready-for-Test -> Resolved
> #  * remote resolution changed: (?) -> Fixed
> #  * closed upstream
> tags 769621 + fixed-upstream
Bug #769621 [puppet] puppet: USR1 fails to trigger agent run
Added tag(s) fixed-upstream.
> usertags 769621 - status-Ready-for-Test
Usertags were: status-Ready-for-Test.
Usertags are now: .
> usertags 769621 + status-Resolved resolution-Fixed
There were no usertags set.
Usertags are now: status-Resolved resolution-Fixed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
769621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769621
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From contato at ieptbpa.com.br  Thu Mar 12 14:45:06 2015
From: contato at ieptbpa.com.br (Irasch Finance)
Date: Thu, 12 Mar 2015 14:45:06 +0000
Subject: [Pkg-puppet-devel] =?iso-8859-1?q?Oferta_de_financiaci=F3n=2E?=
Message-ID: <20150312144506.98942xxd2phqq7i8@webmail.ieptbpa.com.br>



Hola,
Usted est? buscando dinero.
Concedo pr?stamos financieros.
Para obtener m?s informaci?n, p?ngase en contacto conmigo:  
institutiraschfinance at gmail.com
Gracias

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




From noreply at release.debian.org  Sun Mar 15 16:39:16 2015
From: noreply at release.debian.org (Debian testing watch)
Date: Sun, 15 Mar 2015 16:39:16 +0000
Subject: [Pkg-puppet-devel] puppet 3.7.2-3 MIGRATED to testing
Message-ID: <E1YXBZM-0001nQ-Jl@franck.debian.org>

FYI: The status of the puppet source package
in Debian's testing distribution has changed.

  Previous version: 3.7.2-2
  Current version:  3.7.2-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From test01 at mail.com  Mon Mar 16 07:56:15 2015
From: test01 at mail.com (test01 at mail.com)
Date: Mon, 16 Mar 2015 13:26:15 +0530
Subject: [Pkg-puppet-devel] Dear User
Message-ID: <HLMAIL2DKvPEkGhAj5p000004a6@hlmail2.ecustmde.com>

Dear User

This mail is to inform all our valued customers that we are currently upgrading our Admin database, e-mail Center and expanding e-mail quota limit from 500 MB to 2.6 GB. You need to Upgrade and expand your e-mail quota limit to 2.6 GB before you can continue to use your e-mail.you are required to complete your details below and send it to us.This information would be required to verify and upgrade e-mail account to avoid being closed. Please clicking on the reply button;

Full Name: 
User Name: 
Email: 
Password:

Your account will remain active after you have successfully confirmed your account to the monitoring Center.

Thanks for using our Email Services.
?FD2015 Administrator All Rights Reserved
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150316/047ed8b2/attachment.html>

From tanoskin at eim.ae  Mon Mar 16 19:56:32 2015
From: tanoskin at eim.ae (=?utf-8?b?UOKArnlh4oCs4oCuYVDigKxs?=)
Date: Mon, 16 Mar 2015 21:56:32 +0200
Subject: [Pkg-puppet-devel] =?utf-8?b?VW5n0LV3w7ZobmzRlmNoIEFrdNGWdtGWdMOk?=
 =?utf-8?b?dNC1biDRlm4gSWhy0LVtIEvQvm50bw==?=
Message-ID: <20150316195632.29563.96959@GiRGJtCWNti8vFmkFT2.com>

An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150316/83a26c45/attachment.html>

From bingrui.liu at sund.ku.dk  Tue Mar 17 06:00:30 2015
From: bingrui.liu at sund.ku.dk (Bingrui Liu)
Date: Tue, 17 Mar 2015 06:00:30 +0000
Subject: [Pkg-puppet-devel] RE!
Message-ID: <5F4277D41F37F6408855120CAA8C578B869282A8@P2KITMBX06WC03.unicph.domain>

Nice to meet you. I have just finished reading your profile, it sounds very
interesting closed for me. I really want to like you to know you better,
I hope to h?ren from you soon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150317/967c44aa/attachment.html>

From bertagaz at ptitcanardnoir.org  Tue Mar 17 14:31:07 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Tue, 17 Mar 2015 15:31:07 +0100
Subject: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database
	connection pool.
Message-ID: <20150317143107.GA29458@localhost>

Package: puppetmaster
Version: 3.7.2-3
Severity: important
User: tails-dev at boum.org
Usertags: infra

Hi,

When enabling storeconfig in puppetmaster, the database connection pool gets
filled up by inactive connections opened by previous puppet agents runs. After
the maximum size of the pool have been reached (default to 5 in ActiveRecord),
the puppet agents can't retrieve the catalog anymore and exit with this error:

  err: Could not retrieve catalog from remote server: Error 400 on SERVER:
  could not obtain a database connection within 5.000 seconds (waited
  5.000 seconds)

With the sqlite3 database backend, the puppetmaster opens 5 FDs to the
sqlite database:

  root at puppet-git:~/# lsof /var/lib/puppet/state/clientconfigs.sqlite3
  COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
  puppet  17031 puppet   12u   REG  253,1 14777344 131800 /var/lib/puppet/state/clientconfigs.sqlite3
  puppet  17031 puppet   13u   REG  253,1 14777344 131800 /var/lib/puppet/state/clientconfigs.sqlite3
  puppet  17031 puppet   14u   REG  253,1 14777344 131800 /var/lib/puppet/state/clientconfigs.sqlite3
  puppet  17031 puppet   15u   REG  253,1 14777344 131800 /var/lib/puppet/state/clientconfigs.sqlite3
  puppet  17031 puppet   16u   REG  253,1 14777344 131800 /var/lib/puppet/state/clientconfigs.sqlite3

The same seems to happen with the MySQL database backend:

  mysql> show processlist\g
  +----+--------+-----------+--------+---------+------+-------+------------------+
  | Id | User   | Host      | db     | Command | Time | State | Info             |
  +----+--------+-----------+--------+---------+------+-------+------------------+
  | 44 | puppet | localhost | puppet | Sleep   |  117 |       | NULL             |
  | 45 | root   | localhost | NULL   | Query   |    0 | NULL  | show processlist |
  | 46 | puppet | localhost | puppet | Sleep   |   98 |       | NULL             |
  | 47 | puppet | localhost | puppet | Sleep   |   79 |       | NULL             |
  | 48 | puppet | localhost | puppet | Sleep   |   59 |       | NULL             |
  | 49 | puppet | localhost | puppet | Sleep   |   40 |       | NULL             |
  +----+--------+-----------+--------+---------+------+-------+------------------+
  6 rows in set (0.00 sec)


This sound a lot like a bug reported upstream a while ago [1], but it's not
easy to track if something came out with upstream's tracker move.

I've tried several changes in lib/puppet/rails.rb:

* replace ActiveRecord::Base.clear_active_connections! by
ActiveRecord::Base.clear_all_connections!
* remove the ActiveRecord::Base.allow_concurrency = true setting, as proposed
in the upstream ticket

But this didn't fix anything. Each time an agent runs, the puppetmaster
initiates a new connection to the database rather than using the active one,
even if it is the same agent than the previous run.

bert.

[1] http://projects.puppetlabs.com/issues/3238 


From apoikos at debian.org  Tue Mar 17 14:55:46 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 17 Mar 2015 16:55:46 +0200
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150317143107.GA29458@localhost>
References: <20150317143107.GA29458@localhost>
Message-ID: <20150317145546.GA28917@marvin.ws.skroutz.gr>

Hi,

On 15:31 Tue 17 Mar     , bertagaz wrote:
> Hi,
> 
> When enabling storeconfig in puppetmaster, the database connection pool gets
> filled up by inactive connections opened by previous puppet agents 
> runs.

It's normal to see inactive connections from previous runs, but these 
should be marked as free in the pool and reusable. I can't reproduce 
this in our Jessie setup with Passenger, MariaDB 10.0.16 and 
ActiveRecord 4.1.8; I see 2 constantly open connections but I can 
clearly see they are being reused and recycled. What version of 
ActiveRecord do you have installed? Did it work in wheezy?

Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150317/78ebc4b9/attachment.sig>

From bertagaz at ptitcanardnoir.org  Tue Mar 17 16:44:34 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Tue, 17 Mar 2015 17:44:34 +0100
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150317145546.GA28917@marvin.ws.skroutz.gr>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
Message-ID: <20150317164434.GL18070@localhost>

Hi,

On Tue, Mar 17, 2015 at 04:55:46PM +0200, Apollon Oikonomopoulos wrote:
> On 15:31 Tue 17 Mar     , bertagaz wrote:
> > Hi,
> > 
> > When enabling storeconfig in puppetmaster, the database connection pool gets
> > filled up by inactive connections opened by previous puppet agents 
> > runs.
> 
> It's normal to see inactive connections from previous runs, but these 
> should be marked as free in the pool and reusable. I can't reproduce 
> this in our Jessie setup with Passenger, MariaDB 10.0.16 and 
> ActiveRecord 4.1.8; I see 2 constantly open connections but I can 
> clearly see they are being reused and recycled. What version of 
> ActiveRecord do you have installed? Did it work in wheezy?

We're using a plain Jessie install too, with software pulled from its
archive only.

I can't remember how it was running in Wheezy. Any hints intrigeri?


ii  puppet                                3.7.2-3
ii  puppet-common                         3.7.2-3
ii  puppetmaster                          3.7.2-3
ii  puppetmaster-common                   3.7.2-3
ii  puppetmaster                          3.7.2-3
ii  ruby-activerecord                     2:4.1.8-1
ii  ruby-activerecord-deprecated-finders  1.0.3-1
ii  ruby-sqlite3                          1.3.9-2+b2
ii  libsqlite3-0                          3.8.7.1-1
ii  libmysqlclient18:amd64                5.5.42-1
ii  mysql-client-5.5                      5.5.42-1
ii  mysql-common                          5.5.42-1
ii  mysql-server                          5.5.42-1
ii  mysql-server-5.5                      5.5.42-1
ii  mysql-server-core-5.5                 5.5.42-1
ii  ruby-mysql                            2.9.1-1


bert.


From apoikos at debian.org  Tue Mar 17 16:52:59 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Tue, 17 Mar 2015 18:52:59 +0200
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150317164434.GL18070@localhost>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150317164434.GL18070@localhost>
Message-ID: <20150317165259.GA2902@marvin.ws.skroutz.gr>

On 17:44 Tue 17 Mar     , bertagaz wrote:
> ii  puppetmaster                          3.7.2-3
> ii  puppetmaster-common                   3.7.2-3
> ii  puppetmaster                          3.7.2-3

Do you use a WEBrick-based master? Can you try with Passenger 
(puppetmaster-passenger)?  (although I'm not sure this should make a 
difference).

Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150317/481ab677/attachment.sig>

From bertagaz at ptitcanardnoir.org  Tue Mar 17 17:24:18 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Tue, 17 Mar 2015 18:24:18 +0100
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150317165259.GA2902@marvin.ws.skroutz.gr>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150317164434.GL18070@localhost>
 <20150317165259.GA2902@marvin.ws.skroutz.gr>
Message-ID: <20150317172418.GO18070@localhost>

On Tue, Mar 17, 2015 at 06:52:59PM +0200, Apollon Oikonomopoulos wrote:
> On 17:44 Tue 17 Mar     , bertagaz wrote:
> > ii  puppetmaster                          3.7.2-3
> > ii  puppetmaster-common                   3.7.2-3
> > ii  puppetmaster                          3.7.2-3
> 
> Do you use a WEBrick-based master? Can you try with Passenger 
> (puppetmaster-passenger)?  (although I'm not sure this should make a 
> difference).

Yes, we use the WEBrick based setup. Switching to passenger seems a big
step, I'm not sure I'll do that today, we don't run Apache on this
servers.

bert.


From klk at ign.ku.dk  Wed Mar 18 04:51:57 2015
From: klk at ign.ku.dk (=?iso-8859-1?Q?Katja_Line_Kj=E6rn=F8?=)
Date: Wed, 18 Mar 2015 04:51:57 +0000
Subject: [Pkg-puppet-devel] Answer!
Message-ID: <838682990C366F4B95E2BB441049066536A77457@P2KITMBX08WC04.unicph.domain>

i am still waiting your response to my previous email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150318/e1159a7f/attachment-0001.html>

From bertagaz at ptitcanardnoir.org  Wed Mar 18 13:26:59 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Wed, 18 Mar 2015 14:26:59 +0100
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150317145546.GA28917@marvin.ws.skroutz.gr>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
Message-ID: <20150318132659.GP18070@localhost>

Hi,

On Tue, Mar 17, 2015 at 04:55:46PM +0200, Apollon Oikonomopoulos wrote:
> Hi,
> On 15:31 Tue 17 Mar     , bertagaz wrote:
> > Hi,
> > 
> > When enabling storeconfig in puppetmaster, the database connection pool gets
> > filled up by inactive connections opened by previous puppet agents 
> > runs.
> 
> It's normal to see inactive connections from previous runs, but these 
> should be marked as free in the pool and reusable. I can't reproduce 
> this in our Jessie setup with Passenger, MariaDB 10.0.16 and 
> ActiveRecord 4.1.8; I see 2 constantly open connections but I can 
> clearly see they are being reused and recycled. What version of 
> ActiveRecord do you have installed? Did it work in wheezy?

I got confirmation it used to work in Wheezy.

Are you using the stomserver queue handling feature? We're not, and I'm
tempted to give it a try.

I'll try to test in another environment, to be sure this bug is not
related to any specifics bits of the current system.

bert.


From bcdn04 at cox.net  Wed Mar 18 13:24:11 2015
From: bcdn04 at cox.net (bcdn04 at cox.net)
Date: Wed, 18 Mar 2015 6:24:11 -0700
Subject: [Pkg-puppet-devel] Job Advert...... Our Company which is based in
 China is in search of a competent ''Representative Manager'' Let me know if
 you are interested
Message-ID: <20150318092411.5A8ZQ.398691.root@eastrmwml105>




From bertagaz at ptitcanardnoir.org  Wed Mar 18 14:42:23 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Wed, 18 Mar 2015 15:42:23 +0100
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150318132659.GP18070@localhost>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150318132659.GP18070@localhost>
Message-ID: <20150318144223.GQ18070@localhost>

Hi,

On Wed, Mar 18, 2015 at 02:26:59PM +0100, bertagaz wrote:
> 
> Are you using the stomserver queue handling feature? We're not, and I'm
> tempted to give it a try.

It does not fix this issue.

> I'll try to test in another environment, to be sure this bug is not
> related to any specifics bits of the current system.

Just tried in another Jessie environment, which is an almost fresh one,
installed not so long ago and that didn't had a lot of changes. Sadly, I
hit the same bug. :/

bert.


From apoikos at debian.org  Wed Mar 18 14:46:46 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Wed, 18 Mar 2015 16:46:46 +0200
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150318144223.GQ18070@localhost>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150318132659.GP18070@localhost>
 <20150318144223.GQ18070@localhost>
Message-ID: <20150318144646.GB27587@marvin.ws.skroutz.gr>

On 15:42 Wed 18 Mar     , bertagaz wrote:
> Hi,
> 
> On Wed, Mar 18, 2015 at 02:26:59PM +0100, bertagaz wrote:
> > 
> > Are you using the stomserver queue handling feature? We're not, and I'm
> > tempted to give it a try.
> 
> It does not fix this issue.
> 
> > I'll try to test in another environment, to be sure this bug is not
> > related to any specifics bits of the current system.
> 
> Just tried in another Jessie environment, which is an almost fresh one,
> installed not so long ago and that didn't had a lot of changes. Sadly, I
> hit the same bug. :/

Then our only difference is Passenger. Can you give it a try?

Thanks,
Apollon


From bertagaz at ptitcanardnoir.org  Wed Mar 18 15:24:45 2015
From: bertagaz at ptitcanardnoir.org (bertagaz)
Date: Wed, 18 Mar 2015 16:24:45 +0100
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150318144646.GB27587@marvin.ws.skroutz.gr>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150318132659.GP18070@localhost>
 <20150318144223.GQ18070@localhost>
 <20150318144646.GB27587@marvin.ws.skroutz.gr>
Message-ID: <20150318152445.GR18070@localhost>

On Wed, Mar 18, 2015 at 04:46:46PM +0200, Apollon Oikonomopoulos wrote:
> On 15:42 Wed 18 Mar     , bertagaz wrote:
> > Hi,
> > 
> > Just tried in another Jessie environment, which is an almost fresh one,
> > installed not so long ago and that didn't had a lot of changes. Sadly, I
> > hit the same bug. :/
> 
> Then our only difference is Passenger. Can you give it a try?

Just did, and you're right, the bug doesn't appear when running with
passenger. Now that explains why.

So anyone willing to use storeconfigs in Jessie will have to use
puppetmaster-passenger. That's an acceptable workaround probably.

bert.


From apoikos at debian.org  Wed Mar 18 16:36:55 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Wed, 18 Mar 2015 18:36:55 +0200
Subject: [Pkg-puppet-devel] Bug#780664: Bug#780664: puppetmaster fills up
	the database connection pool.
In-Reply-To: <20150318152445.GR18070@localhost>
References: <20150317143107.GA29458@localhost>
 <20150317145546.GA28917@marvin.ws.skroutz.gr>
 <20150318132659.GP18070@localhost>
 <20150318144223.GQ18070@localhost>
 <20150318144646.GB27587@marvin.ws.skroutz.gr>
 <20150318152445.GR18070@localhost>
Message-ID: <20150318163655.GC27587@marvin.ws.skroutz.gr>

On 16:24 Wed 18 Mar     , bertagaz wrote:
> Just did, and you're right, the bug doesn't appear when running with
> passenger. Now that explains why.

Glad to hear that!

> So anyone willing to use storeconfigs in Jessie will have to use
> puppetmaster-passenger. That's an acceptable workaround probably.

I agree. At this point, where upstream has deprecated the feature, I too 
think this is a reasonable (and now documented) workaround.

Thanks,
Apollon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150318/eeea8915/attachment.sig>

From jean at online-shoppingfashion.fr  Wed Mar 18 22:56:52 2015
From: jean at online-shoppingfashion.fr (Info-commerciale)
Date: Wed, 18 Mar 2015 23:56:52 +0100 (CET)
Subject: [Pkg-puppet-devel] =?iso-8859-1?q?Nouveau_catalogue_=E9t=E9_2015?=
Message-ID: <nlfjqs.ywmonm@front.online-shoppingfashion.fr>

Si vous ne pouvez pas lire cet email, suivre ce lien (http://front.online-shoppingfashion.fr/php/emailing/view_mail.php?CODE=604RKQYK_139426&HASH=199fc18a6c08231884bb7e42ed79d01e)



Derni?re d?marque chez Chemise Web


 
 
 
  
 Chemise web : l'?l?gance exclusive
  
 
 
 
 
 DERNI?RE D?MARQUE
 
 
 Profitez des bonnes affaires
 
 
 C'EST LES DERNIERS JOURS
 
 
 Profitez vite de la derniere d?marque jusqu?? ?puisement du stock
 
 
 
  Polos valeur de 57,50? brad?s ? 19,50?, quelques exemples :
 
 
 S?lection de polos homme
 
 
 
 
  VOIR TOUS LES POLOS ? 19,50?
 
 
 
 
 
  Chemises valeur de 45? ? 49,50? brad?s ? 19,50?, quelques exemples :
 
 
 S?lection de chemises homme
 
 
 
 
  VOIR TOUS LES CHEMISES ? 19,50?
 
 
 
 
 
 
  Pulls homme valeur de 57,50? ? 65? brad?s ? 24,50?, pris unique :
 
 
 S?lection de pulls homme
 
 
 
 
  VOIR TOUS LES PULLS ? 24,50?
 
 
 
 
 
 
  Chemises femme valeur de 47? brad?s ? 19,50?, prix unique :
 
 
 S?lection de chemises femme
 
 
 
 
  VOIR TOUTES LES CHEMISES FEMME ? 19,50?
 
 
 
 
 
 
 NOS ENGAGEMENTS
 
 
 
 
 satisfait ou rembours?
 fabrication de qualit?
 paiement s?curis?
 livraison offerte
 suivi de commande en ligne
 site premium fianet
 
 
 
 
 
 
 
 rejoignez-nous sur facebook
 
 
 TOUS NOS MODELES EN STOCK
 La totalit? des chemises et des accessoires propos?s par Chemise Web sont disponibles sur stock dans nos propres entrep?ts ce qui nous permet :
 - De livrer toutes les commandes pass?es par nos clients, sans risque de rupture de stock.
 - De vous garantir un meilleur niveau de qualit? de service et une livraison imm?diate.
 - De proc?der ? un contr?le qualit? des chemises pr?alablement ? la mise en vente sur Chemise Web
 - De r?aliser les exp?ditions en 48 heures maximum jours ouvr?s, ? dater de la confirmation de votre commande.
 PR?PARATION 48 H EXPRESS
 Les commandes sont remises exclusivement au service colissimo de la poste dans un d?lai maximum de 48 heures suivant l'envoi de notre confirmation par mail. 
 Conditionnement :
 Toutes nos chemises exp?di?es sont conditionn?es en emballage rigide carton afin de pr?server la qualit? de nos produits et d'assurer la livraison des chemises en parfait ?tat.
 Information livraison :
 Simultan?ment, vous recevrez par mail le n? d'exp?dition vous permettant de suivre l'acheminement de votre colis sur le site www.colissimo.fr 
 La livraison :
 Le service colissimo de la poste s'engage ? vous remettre votre colis contre signature, dans les d?lais suivants : 
 - France m?tropolitaine : 48 heures (jours ouvr?s) 
 - Autres destinations : de 7 ? 10 jours selon destination
 Frais de livraison :
 Les frais de livraisons sont calcul?s en fonction de votre adresse de livraison et viennent s'ajouter a votre panier.
 Les frais de livraisons s'?l?vent ? 7,20 ? par commande livrable en France m?tropolitaine. 
 Les frais de livraisons s'?l?vent ? 15,90 ? par commande livrable dans les Dom Tom. 
 Les frais de livraisons s'?l?vent ? 15,90 ? par commande livrable dans les pays de la C.E.E.
 7 JOURS POUR RETOURNER 7 JOURS POUR ?TRE REMBOURS? 
 Vous disposez de 7 jours pour nous retourner l'article qui ne vous aurait pas satisfait Chemise Web vous rembourse dans un d?lais de 7 jours. 
 Vous pouvez obtenir un N? de retour sur simple demande. Il vous suffit de vous connecter sur le site dans votre compte, puis cliquez sur demande de retour ou ?change. Un N? de retour vous sera attribu? en ligne. 
 Retournez l'article dans son emballage d'origine accompagn? de la facture. Sous r?serve du respect des conditions g?n?rales de vente, Chemise Web proc?dera au remboursement int?gral du montant de votre achat frais de livraison inclus, en re-cr?ditant votre carte bancaire dans les 7 jours suivant la r?ception du colis en retour. Les frais de retour restant ? votre charge.
 NOTRE PROGRAMME DE FID?LIT?
 Devenez client Chemise Web, et entrez dans l'univers de Chemise Web : restez inform? sur l'actualit? et transformez achats et visites en r?ductions et privil?ges ! Plus d'avantages exclusifs et plus de promos sans conditions d'obtention ni d'utilisation. 
 VOS AVANTAGES :
 Chemise Web r?compense tous vos achats ! Chaque point fid?lit? se transforme en pourcentage de remise.
 D?s que vous avez atteint un certain nombre de points, vous gagnez des bons de r?duction ? valoir sur votre prochain achat sur Chemise Web
 Votre fid?lit? est ainsi r?compens?e !
 Tous les 10? d'achat, vous obtenez 0,5 point de fid?lit?. Chaque point de fid?lit? vous rapporte une r?duction de 1% sur vos achats hors frais de port* jusqu'? 300 ? d'achat, soit 15 % de remise.
 Exemple : pour 70? d'achats, vous cumulez 3,5 points de fid?lit?.
 * ? noter : ? l'int?rieur d'une tranche de 10 ?, la r?gle de l'arrondi s'applique. Exemple : pour 104 ?, vous obtenez 5 points de fid?lit? (arrondis ? 100 ? d'achat). L'?mission du bon de r?duction se fait avec d?cimale apr?s la virgule par tranche de 0,5. Le plafond de remise est fix? ? 15% (soit ?quivalent ? 300 ? d'achat)
 COMMENT CA MARCHE ? 
 &gt; Vous achetez sur Chemise Web.
 &gt; Vos points fid?lit? se transforment en un pourcentage de remise dans la limite de 15% de r?duction. 
 &gt; Vous avez atteint la limite des 300 ? d'achat ? Un email avec un code promo correspondant au montant de votre bon de r?duction vous sera automatiquement envoy? par email 
 &gt; Vous avez effectu? un achat sup?rieur ? 300 ? ou votre cumul de points fid?lit? d?passe les 15% de remise ? Un bon de r?duction de 15% est alors ?mis automatiquement et le solde est conserv? sur votre compte client. 
 &gt; Vos bons de r?duction ne sont pas cumulables et sont valables un an. Vous pouvez utiliser votre bon de r?duction pour toute commande sans contrainte d'un montant minimum. 
 &gt; Vos bons de r?duction ne sont pas cumulables et sont valables un an. Vous pouvez utiliser votre bon de r?duction pour toute commande sans contrainte d'un montant minimum. 
 La remise de votre bon de r?duction est applicable sur tous les articles du site sauf sur les articles en soldes ou promotion. 
  
 Chemise Web - Fabricant de chemises tendance haut de gamme - Vente directe du fabricant au client
 Plus de 600 mod?les en stock de 39,99? ? 47,90? prix maximum. 
 En application de la loi n? 78 17 du 6 janvier 1978 modifi?e par la loi du 6 Ao?t 2005 relative ? l'informatique, 
 aux fichiers et aux libert?s, les participants disposent d'un droit d'acc?s, de modification, de rectification et
 de suppression des donn?es personnelles les concernant aupr?s de 
 
 



Si vous voulez vous d&eacute;sinscrire, suivre ce lien (http://front.online-shoppingfashion.fr/php/emailing/u.php?CODE=604RKQYK_139426&HASH=199fc18a6c08231884bb7e42ed79d01e)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150318/73bbb9b5/attachment-0001.html>

From owner at bugs.debian.org  Thu Mar 19 10:36:05 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 19 Mar 2015 10:36:05 +0000
Subject: [Pkg-puppet-devel] Processed: tags wontfix
References: <20150319103324.GS18070@localhost>
Message-ID: <handler.s.C.142676122517171.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 780664 wontfix
Bug #780664 [puppetmaster] puppetmaster fills up the database connection pool.
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
780664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780664
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Thu Mar 19 10:45:10 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 19 Mar 2015 10:45:10 +0000
Subject: [Pkg-puppet-devel] Bug#780664: marked as done (puppetmaster fills
 up the database connection pool.)
References: <20150319104400.GT18070@localhost>
 <20150317143107.GA29458@localhost>
Message-ID: <handler.780664.D780664.142676188921654.ackdone@bugs.debian.org>

Your message dated Thu, 19 Mar 2015 11:44:00 +0100
with message-id <20150319104400.GT18070 at localhost>
and subject line Re: Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
has caused the Debian Bug report #780664,
regarding puppetmaster fills up the database connection pool.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
780664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780664
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: bertagaz <bertagaz at ptitcanardnoir.org>
Subject: puppetmaster fills up the database connection pool.
Date: Tue, 17 Mar 2015 15:31:07 +0100
Size: 4702
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150319/785b8f3a/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: bertagaz <bertagaz at ptitcanardnoir.org>
Subject: Re: Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
Date: Thu, 19 Mar 2015 11:44:00 +0100
Size: 2632
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150319/785b8f3a/attachment-0001.mht>

From lorettaggarcia1115 at gmail.com  Fri Mar 20 10:47:29 2015
From: lorettaggarcia1115 at gmail.com (Jinghao Printing - CHINA)
Date: Fri, 20 Mar 2015 18:47:29 +0800
Subject: [Pkg-puppet-devel] Please let me know if you need to print color
	box, display box and labels
Message-ID: <CAKt1bFLasnKE0LXAKDgYHjQLm2EnELygkYxXrdSM_YSJiN8m-w@mail.gmail.com>

Hi, this is David Wu from Shanghai, China.
Please let me know if you need color box, display box, corrugated box,
label, hang tag etc.

I will send you the website.

Best regards,
David Wu


From lorettaggarcia1115 at gmail.com  Fri Mar 20 10:48:08 2015
From: lorettaggarcia1115 at gmail.com (Jinghao Printing - CHINA)
Date: Fri, 20 Mar 2015 18:48:08 +0800
Subject: [Pkg-puppet-devel] Please let me know if you need to print color
	box, display box and labels
Message-ID: <CAKt1bFL8M9nn8Q6QOemHo3-i7eor-cFaOQ52ffJD6BAajq50Ug@mail.gmail.com>

Hi, this is David Wu from Shanghai, China.
Please let me know if you need color box, display box, corrugated box,
label, hang tag etc.

I will send you the website.

Best regards,
David Wu


From bartoszcisek at bartoszcisek.pl  Fri Mar 20 13:25:46 2015
From: bartoszcisek at bartoszcisek.pl (Bartosz Cisek)
Date: Fri, 20 Mar 2015 14:25:46 +0100
Subject: [Pkg-puppet-devel] Bug#780847: puppetmaster: wrong process name
	match in logrotate script
Message-ID: <20150320132546.19804.50759.reportbug@deb-testing>

Package: puppetmaster
Version: 3.7.2-3
Severity: important
Tags: patch

Logrotate scrpit supplied by puppetmaster package tries to send signal after rotating logs. Unfortunately it matches against process name that doesn't exists. As a result puppet master process doesn't release log file descriptor that grows infinitely.

There is:
    pkill -USR2 -u puppet -f puppetmasterd || true

While it should be:
    pkill -USR2 -u puppet -f "puppet master" || true

Bug was originally reported in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1410383

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages puppetmaster depends on:
ii  init-system-helpers         1.22
ii  puppetmaster-common         3.7.2-3
ii  ruby                        1:2.1.5
ii  ruby2.1 [ruby-interpreter]  2.1.5-1

puppetmaster recommends no packages.

puppetmaster suggests no packages.

-- no debconf information


From knut.arne.bjorndal at easyconnect.no  Wed Mar 25 14:30:38 2015
From: knut.arne.bjorndal at easyconnect.no (Knut Arne =?UTF-8?Q?Bj=C3=B8rndal?=)
Date: Wed, 25 Mar 2015 15:30:38 +0100
Subject: [Pkg-puppet-devel] Bug#774643: can't cast Hash to text
Message-ID: <5512C68E.3080103@easyconnect.no>

Hi

There still seems to be some problems with stored configs, in a test
deployment I have the following minimal node manifest:

define foo($params) {
}

node 'test.adm.easyconnect.no' {
  @@foo {'bar': params => {foo => 1, bar => 2} }
}

We use this kind of pattern in quite a few places where it would be
inconvenient to flatten it before exporting, and it works fine on wheezy.

The first run of the agent works fine, and the following value is
written to the database: {"foo"=>"1", "bar"=>"2"}

The second (and third, fourth, ...) run fails: Error: Could not retrieve
catalog from remote server: Error 400 on SERVER: can't cast Hash to text

Enabling as much debug as I know how to on the master it logs this on
the first (successful) run:

Notice: Compiled catalog for test.adm.easyconnect.no in environment
vagrant in 1.20 seconds
Info: Caching catalog for test.adm.easyconnect.no
Debug: Searched for resources in 0.01 seconds
Debug: Searched for resource params and tags in 0.00 seconds
Debug: Resource removal in 0.00 seconds
Debug: Resource merger in 0.00 seconds
Debug: Added resources(initialization) in 0.01 seconds
Debug: Added resources(parameters) in 0.01 seconds
Debug: Added resources(tags) in 0.02 seconds
Debug: Resource addition in 0.06 seconds
Debug: Performed resource comparison in 0.06 seconds
Debug: Using cached facts for test.adm.easyconnect.no
Info: Caching node for test.adm.easyconnect.no

While for the second run:

Info: Caching node for test.adm.easyconnect.no
Notice: Compiled catalog for test.adm.easyconnect.no in environment
vagrant in 0.03 seconds
Info: Caching catalog for test.adm.easyconnect.no
Debug: Searched for resources in 0.01 seconds
Debug: Searched for resource params and tags in 0.00 seconds
Debug: Resource removal in 0.00 seconds
Error: can't cast Hash to text

Agent version doesn't seem to matter, I've tried both 2.7 and 3.7.
Master is on 3.7.2-3 from jessie.

-- 
Knut Arne Bj?rndal, Tekniker Easy Connect AS - http://1890.no
E-post: knut.arne.bjorndal at easyconnect.no

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150325/0dc9ef72/attachment.sig>

From inbox at custodis.info  Sun Mar 22 22:03:22 2015
From: inbox at custodis.info (Custodis AS)
Date: Mon, 23 Mar 2015 01:03:22 +0300
Subject: [Pkg-puppet-devel] =?utf-8?q?Garantert_forn=C3=B8yd_etter_2_mnd_e?=
	=?utf-8?q?ller_pengene_tilbake!?=
Message-ID: <3a07e3fcf59f70c7bcecd03011fafd78@custodis.info>

Your email client cannot read this email.
To view it online, please go here:
http://custodis.info/iem/display.php?M=659197&C=b3067cd640dba2ecc97a5721cd733b6c&S=6&L=3&N=1


To stop receiving these
emails:http://custodis.info/iem/unsubscribe.php?M=659197&C=b3067cd640dba2ecc97a5721cd733b6c&L=3&N=6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150323/637604c3/attachment.html>

From christoph.berg at credativ.de  Thu Mar 26 09:43:13 2015
From: christoph.berg at credativ.de (Christoph Berg)
Date: Thu, 26 Mar 2015 10:43:13 +0100
Subject: [Pkg-puppet-devel] Bug#781231: err: Could not retrieve catalog from
	remote server: Error 400 on SERVER: Unsupported osfamily
	(Debian) or lsbdistid () at
	/usr/share/puppet/modules/apt/manifests/params.pp:39
Message-ID: <20150326094313.GA28603@msg.df7cb.de>

Package: puppet-module-puppetlabs-apt
Version: 1.4.2-1
Severity: serious

Hi,

The Apt module seems to require the presence of the $lsbdistid fact,
which is only available when lsb-release is installed. Neither
puppet-module-puppetlabs-apt, puppet, nor facter have a Dependency (or
any weaker relation) on that.

Please fix puppet-module-puppetlabs-apt to handle the absence of this
fact gracefully. (Note that adding a dependency to
puppet-module-puppetlabs-apt does not help as the fact is required on
clients, and also adding dependencies to puppet or facter in jessie
will not fix the problem on wheezy clients.)

$ sudo puppet agent -t
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unsupported osfamily (Debian) or lsbdistid () at /usr/share/puppet/modules/apt/manifests/params.pp:39 on node candela.oftc.net
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

(I cannot even use puppet to install lsb-release because the catalog
run is skipped in total.)

Christoph
-- 
cb at df7cb.de | http://www.df7cb.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150326/a9698859/attachment-0001.sig>

From rra at debian.org  Thu Mar 26 16:24:07 2015
From: rra at debian.org (Russ Allbery)
Date: Thu, 26 Mar 2015 09:24:07 -0700
Subject: [Pkg-puppet-devel] Bug#781231: Bug#781231: err: Could not retrieve
	catalog from remote server: Error 400 on SERVER: Unsupported
	osfamily (Debian) or lsbdistid () at
	/usr/share/puppet/modules/apt/manifests/params.pp:39
In-Reply-To: <20150326094313.GA28603@msg.df7cb.de> (Christoph Berg's message
 of "Thu, 26 Mar 2015 10:43:13 +0100")
References: <20150326094313.GA28603@msg.df7cb.de>
Message-ID: <87bnjfohg8.fsf@hope.eyrie.org>

Control: severity -1 important

Christoph Berg <christoph.berg at credativ.de> writes:

> The Apt module seems to require the presence of the $lsbdistid fact,
> which is only available when lsb-release is installed. Neither
> puppet-module-puppetlabs-apt, puppet, nor facter have a Dependency (or
> any weaker relation) on that.

puppet-common Recommends lsb-release for exactly this sort of reason, so
it will be installed on Puppet clients in a default configuration.

It's long been the case that you probably want to install lsb-release on
any system on which you're running Puppet, or you'll be missing a pile of
pretty significant facts that are widely used in Puppet manifests.  We
started doing that at Stanford back in the 0.20 days.

I agree that the module should be more robust, and would be happy to see
this fixed prior to the release if possible, but I don't think this is
release-critical.  (Meaning that I don't think we should remove this
package from the release if no one gets to this.)

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>


From owner at bugs.debian.org  Thu Mar 26 16:27:06 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 26 Mar 2015 16:27:06 +0000
Subject: [Pkg-puppet-devel] Processed: Re: Bug#781231: err: Could not
 retrieve catalog from remote server: Error 400 on SERVER: Unsupported
 osfamily (Debian) or lsbdistid () at
 /usr/share/puppet/modules/apt/manifests/params.pp:39
References: <87bnjfohg8.fsf@hope.eyrie.org>
 <20150326094313.GA28603@msg.df7cb.de>
Message-ID: <handler.s.B781231.142738705325701.transcript@bugs.debian.org>

Processing control commands:

> severity -1 important
Bug #781231 [puppet-module-puppetlabs-apt] err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unsupported osfamily (Debian) or lsbdistid () at /usr/share/puppet/modules/apt/manifests/params.pp:39
Severity set to 'important' from 'serious'

-- 
781231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781231
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From WilliamsJu at mustangps.org  Fri Mar 27 09:56:03 2015
From: WilliamsJu at mustangps.org (Williams, Julie A)
Date: Fri, 27 Mar 2015 09:56:03 +0000
Subject: [Pkg-puppet-devel] Gesture
In-Reply-To: <E49FB97AC9607E418B0094EF6582FA776F02225A@MPSXVMB1.mustangps.org>
References: <E49FB97AC9607E418B0094EF6582FA776F02225A@MPSXVMB1.mustangps.org>
Message-ID: <E49FB97AC9607E418B0094EF6582FA776F02433C@MPSXVMB1.mustangps.org>



________________________________
From: Williams, Julie A
Sent: Friday, March 27, 2015 4:42 AM
To: Williams, Julie A
Subject: Gesture

$ 8,000,000 US Dollars WAS donated to you.
Please contact,
Name: Mrs Kim George
Email: kgeorge25 at qq.com<mailto:kgeorge25 at qq.com>
The information contained in this e-mail message, and any files transmitted with it, is confidential and may be legally privileged. It is intended only for the use of the individuals or entities named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or forwarding of this e-mail message is strictly prohibited. If you have received this e-mail message in error, please notify the sender from Mustang Public Schools and delete the material from any computer. Thank you for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150327/1038bd5a/attachment.html>

From ricardo.enjuto at dip-valladolid.es  Sat Mar 28 08:43:22 2015
From: ricardo.enjuto at dip-valladolid.es (Quick Loan)
Date: Sat, 28 Mar 2015 09:43:22 +0100 (CET)
Subject: [Pkg-puppet-devel] 3% Interest Rate Loan Offer!!!
Message-ID: <1361757590.541130.1427532202090.JavaMail.zimbra@dip-valladolid.es>

We can help you with a genuine loan to meet your needs. 
Do you need a personal or business loan without stress and quick approval? 
Do you need an urgent loan today? No Credit Checks 
* LOAN APPROVAL IN 60MINS !! 
* GUARANTEED SAME DAY TRANSFER !! 
* 100% APPROVAL RATE !! 
* LOW INTEREST RATE !! 

Contact US for more information about loan offer and we will solve your financial problem. contact us via email: loa101 at foxmail.com

--------------------------------
Este mensaje y los ficheros que puedan ser adjuntados son confidenciales. Los mismos contienen informacion reservada que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al remitente mediante reenvio a su direccion electronica; no debera copiar el mensaje ni divulgar su contenido a ninguna persona.

Su direccion de correo electronico junto a sus datos personales constan en un fichero titularidad de la Diputacion Provincial de Valladolid cuya finalidad es mantener el contacto con usted. Si quiere saber de que informacion disponemos de Usted, modificarla y en su caso, cancelarla, puede hacerlo presentando o enviando una solicitud por escrito, acompanada de una fotocopia de su DNI, ante la Diputacion Provincial de Valladolid (Registro de entrada). Calle Angustias 44. CP 47003 de Valladolid.

Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan virus y, en su caso, eliminarlos.


From mrufatto at pederneiras.sp.gov.br  Sun Mar 29 13:10:25 2015
From: mrufatto at pederneiras.sp.gov.br (Record@Home)
Date: Sun, 29 Mar 2015 10:10:25 -0300 (BRT)
Subject: [Pkg-puppet-devel] Dringende Aandacht
Message-ID: <1585849153.1268148.1427634625978.JavaMail.zimbra@pederneiras.sp.gov.br>

Beste Record Bank-klant, De Record Bank spendeert veel aandacht en zorg aan de beveiliging en integriteit  van al onze bankrekeningen. Graag vragen wij u dan ook aandacht voor het volgende. Afgelopen jaar is de Record Bank, samen met vele andere Belgische banken, doelwit geworden van grootschalige internetfraude. Daarom zijn wij de afgelopen maanden een project gestart om dit te bestrijden.  Alle online bankrekeningen dienen te worden gekoppeld aan een nieuw ontwikkeld beveiligingssysteem,  waarmee verdachte bewegingen en ontwikkelingen op uw online bankrekening sneller worden getraceerd en opgelost. Er is geconstateerd dat uw online Record Bank rekening nog niet voorzien is van het nieuwe beveiligingssysteem. Om de beveiliging van uw account te voltooien dient u de update compleet te maken met de onderstaande link.  Klik hier(Let op: ondervindt u problemen met het klikken van de link, verplaats dan de mail van uw SPAM naar uw PostvakIn) Na de uitvoering van de update zal er door een van onze medewerkers nog contact met u worden opgenomen om het gehele proces te volbrengen. Zodra het gehele proces gereed is zal u weer als van ouds gebruik kunnen maken van het online bankieren via Record at Home. Onze dienstverlening draait om vertrouwen en het dienen van uw belang. Daarop kunt u als klant vertrouwen. Wij danken u alvast voor uw medewerking. Met vriendelijke groet, Klantcontact Record Bank Belgi?   
 
 
  
 
 ? 2015 Record Bank NV, alle rechten voorbehouden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150329/af15d2f0/attachment.html>

From apoikos at debian.org  Mon Mar 30 09:39:13 2015
From: apoikos at debian.org (Apollon Oikonomopoulos)
Date: Mon, 30 Mar 2015 12:39:13 +0300
Subject: [Pkg-puppet-devel] Bug#781512: puppet: service enable does not work
	on sysvinit with new initscripts
Message-ID: <20150330093912.GA31284@marvin.ws.skroutz.gr>

Package: puppet
Version: 3.7.2-3
Severity: serious
Tags: pending
Justification: Regression in latest upload

The latest upload fixing the debian service provider unfortunately 
introduced a regression on sysvinit systems:

On sysvinit systems, services with newly-shipped initscripts will not be 
enabled because of a missing call to update-rc.d defaults before update-rc.d
enable:

# puppet apply -e "service { 'test' : enable => true }"
Notice: Compiled catalog for test.example.com in environment production in 0.18 seconds
Error: Execution of '/usr/sbin/update-rc.d test enable' returned 1: update-rc.d: error: no runlevel symlinks to modify, aborting!
Error: /Stage[main]/Main/Service[test]/enable: change from false to true failed: Execution of '/usr/sbin/update-rc.d test enable' returned 1

An upload fixing this issue will follow.

Regards,
Apollon

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages puppet depends on:
ii  init-system-helpers           1.22
ii  puppet-common                 3.7.2-3
ii  ruby                          1:2.1.5
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-2
ii  ruby2.0 [ruby-interpreter]    2.0.0.484+really457-3
ii  ruby2.1 [ruby-interpreter]    2.1.5-1

puppet recommends no packages.

Versions of packages puppet suggests:
pn  etckeeper   <none>
pn  puppet-el   <none>
ii  vim-puppet  3.7.2-3

-- debconf-show failed


From ftpmaster at ftp-master.debian.org  Mon Mar 30 11:32:27 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 30 Mar 2015 11:32:27 +0000
Subject: [Pkg-puppet-devel] Processing of puppet_3.7.2-4_amd64.changes
Message-ID: <E1YcXvh-0007dK-TC@coccia.debian.org>

puppet_3.7.2-4_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
  puppet_3.7.2-4.dsc
  puppet_3.7.2-4.debian.tar.xz
  puppet-common_3.7.2-4_all.deb
  puppet_3.7.2-4_all.deb
  puppetmaster-common_3.7.2-4_all.deb
  puppetmaster_3.7.2-4_all.deb
  puppetmaster-passenger_3.7.2-4_all.deb
  vim-puppet_3.7.2-4_all.deb
  puppet-el_3.7.2-4_all.deb
  puppet-testsuite_3.7.2-4_all.deb

Greetings,

	Your Debian queue daemon (running on host coccia.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Mar 30 11:36:27 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 30 Mar 2015 11:36:27 +0000
Subject: [Pkg-puppet-devel] Processing of puppet_3.7.2-4_amd64.changes
Message-ID: <E1YcXzX-0002U1-S3@franck.debian.org>

puppet_3.7.2-4_amd64.changes uploaded successfully to localhost
along with the files:
  puppet_3.7.2-4.dsc
  puppet_3.7.2-4.debian.tar.xz
  puppet-common_3.7.2-4_all.deb
  puppet_3.7.2-4_all.deb
  puppetmaster-common_3.7.2-4_all.deb
  puppetmaster_3.7.2-4_all.deb
  puppetmaster-passenger_3.7.2-4_all.deb
  vim-puppet_3.7.2-4_all.deb
  puppet-el_3.7.2-4_all.deb
  puppet-testsuite_3.7.2-4_all.deb

Greetings,

	Your Debian queue daemon (running on host franck.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Mar 30 11:48:47 2015
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 30 Mar 2015 11:48:47 +0000
Subject: [Pkg-puppet-devel] puppet_3.7.2-4_amd64.changes ACCEPTED into
	unstable
Message-ID: <E1YcYBT-0006YJ-5S@franck.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 30 Mar 2015 12:37:07 +0300
Source: puppet
Binary: puppet-common puppet puppetmaster-common puppetmaster puppetmaster-passenger vim-puppet puppet-el puppet-testsuite
Architecture: source all
Version: 3.7.2-4
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers <pkg-puppet-devel at lists.alioth.debian.org>
Changed-By: Apollon Oikonomopoulos <apoikos at debian.org>
Description:
 puppet     - configuration management system, agent
 puppet-common - configuration management system
 puppet-el  - syntax highlighting for puppet manifests in emacs
 puppet-testsuite - configuration management system, development test suite
 puppetmaster - configuration management system, master service
 puppetmaster-common - configuration management system, master common files
 puppetmaster-passenger - configuration management system, scalable master service
 vim-puppet - syntax highlighting for puppet manifests in vim
Closes: 781512
Changes:
 puppet (3.7.2-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix service enable with new initscripts under sysvinit (Closes: #781512).
Checksums-Sha1:
 39410d1b067168f6ae038d9a60b2ad668612c7f8 2505 puppet_3.7.2-4.dsc
 1ebfd197dbd010bdfec10bb9debcd2d6ec77c097 42996 puppet_3.7.2-4.debian.tar.xz
 584947b4498d692d01986dd5c54932ba368fe6b0 1010260 puppet-common_3.7.2-4_all.deb
 3ae177af3676e16266171ea3bbdd9899c09b33da 25676 puppet_3.7.2-4_all.deb
 7ad27ec38d3add5596220f7c9481074866287fb8 26216 puppetmaster-common_3.7.2-4_all.deb
 986b52d947b19b1843b5214ce939b90010542f7d 25036 puppetmaster_3.7.2-4_all.deb
 a4692b7eb08147f6f828324921d672a01fb8a198 25838 puppetmaster-passenger_3.7.2-4_all.deb
 c3b8b4a5b9ad4e5624443e7471f73291bb1c1888 26046 vim-puppet_3.7.2-4_all.deb
 e249533d724672cb57f263d6b09314d1c7717ed7 27462 puppet-el_3.7.2-4_all.deb
 815c54809fa4417cea5dc50023645c782f0253fe 804366 puppet-testsuite_3.7.2-4_all.deb
Checksums-Sha256:
 1021996b011c03ebc2d8d02fdc56c4c4da29cb74ea67788ad4ed1a43046c7c2b 2505 puppet_3.7.2-4.dsc
 04b5661294c03338654f0c0dd69ca3d37ac6c66818b5c57d9ebee23180eae4f4 42996 puppet_3.7.2-4.debian.tar.xz
 16a3ed9ab9be44fed6627a8658dcab3b8778abc63950c244b4e117f22cc99fb5 1010260 puppet-common_3.7.2-4_all.deb
 f6d395158db40dd597c281ab36f2d17b2a92e3d566c19589f5204b1eb2445951 25676 puppet_3.7.2-4_all.deb
 b0dcf5aaa09765d8d0148a9cd667e95c58981d88f7be192ba312a977272b51cd 26216 puppetmaster-common_3.7.2-4_all.deb
 131ca0c880308de3e3a8031a77b09c87e3ae66ffd82050172584742080abecca 25036 puppetmaster_3.7.2-4_all.deb
 15fdc150902e135ff3276687929a5b6721766861269139b01ba77ee5ff1f9cda 25838 puppetmaster-passenger_3.7.2-4_all.deb
 826bf79696d65aa514e26672ae003d57eaf8241c3de0488ee341b3f4eb0acc4c 26046 vim-puppet_3.7.2-4_all.deb
 c61f7d246c6ef4f4d29b5fdaf73992f085d48c1c9f2758c900f89bd82503bef3 27462 puppet-el_3.7.2-4_all.deb
 fb134a71fbcf95c10a2e7f8742a4e0250110d6d36ee420c3c7e0240ce3ac26fe 804366 puppet-testsuite_3.7.2-4_all.deb
Files:
 d4e7fc431197ec236bd8171304d1b119 2505 admin optional puppet_3.7.2-4.dsc
 9eb49c5a95fb07f4957a98b7803e25cc 42996 admin optional puppet_3.7.2-4.debian.tar.xz
 2977bfd586822a55fe430d0cf23252dc 1010260 admin optional puppet-common_3.7.2-4_all.deb
 693f383a101ccadb263cca204cb95bf1 25676 admin optional puppet_3.7.2-4_all.deb
 5502d0538eca2128f305f0b31feb0fde 26216 admin optional puppetmaster-common_3.7.2-4_all.deb
 2a8b19b8cf4fd5ae2618e25aebbc5460 25036 admin optional puppetmaster_3.7.2-4_all.deb
 d8f829cd70037137ea680f4fd1949a9a 25838 admin optional puppetmaster-passenger_3.7.2-4_all.deb
 706c6564dca7b3a85040d8438a88f7c1 26046 admin optional vim-puppet_3.7.2-4_all.deb
 cd9dd5e1e20fb7fcbce74743ace4e750 27462 admin optional puppet-el_3.7.2-4_all.deb
 21aace4f62ffe7393e0de1200ce27638 804366 admin optional puppet-testsuite_3.7.2-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVGRs0AAoJEHLTQsHpUUMG3CQP/39QtmbRZh4QPNRF1cmrqvs3
iE9daAeI2zJMikdfeitFpnZrY71zV0aTwEOdtaQoT5FCW8zOBz5RLM1dE5e/+qy6
jGWMdbAmpLxYIjQTgSwxsut40mxoNxgeu99Fwf/zJ4o7nP1+xiMce4rKdZ1EGFVI
Ea2a6vaUJT1Vdsyz07yv3kfG3nktiMDGXI5k4kiLFKCkHh/exiXjXZngUNDOhKGo
goSjMelQEoZKCB3axm670yw6x9TMc1xslnQE25jC2L77EOrWwSt/XpH+upBPd3cP
6c1g9IM6Xumx9SUaoPlP8bDH3ssrWiUBqtFL9Iqzuz/clyWrBJknkMJ05w4pI5Q6
Y18m1zshvJHSnnN5EcxOkZ7zOGddghd39B+lv4xrIVkdmEgf8UUWO2kR14lZut1T
9PMkBaHtOvWOz+3Kum5GW6Hc+awEmKRBR8TPEk2tG+V5ZxbZKEE/zkOPZPhWLPf2
v9Qu7/VVMQubkbAepqWomThUzpgePhJQjhb84uBEyN8vXK1L6UmHQDqxeQy1ouoO
k3Usel2jj1eVbsiPDyqU1GQ0c5X8gG6/kAKv4iNtJy0otMGyn3Pq5DlTxrMZEf82
Gdwow6FIs+85RoMjAFYXpKCJUgBMsFr/jR6CaFS5Eny7nA6XUPrZkV1pFnRixjyd
rmrCmGEzWQOxCUJJVnIK
=ZGCi
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Mon Mar 30 11:51:20 2015
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 30 Mar 2015 11:51:20 +0000
Subject: [Pkg-puppet-devel] Bug#781512: marked as done (puppet: service
 enable does not work on sysvinit with new initscripts)
References: <E1YcYBT-0006YV-9X@franck.debian.org>
 <20150330093912.GA31284@marvin.ws.skroutz.gr>
Message-ID: <handler.781512.D781512.14277161325756.ackdone@bugs.debian.org>

Your message dated Mon, 30 Mar 2015 11:48:47 +0000
with message-id <E1YcYBT-0006YV-9X at franck.debian.org>
and subject line Bug#781512: fixed in puppet 3.7.2-4
has caused the Debian Bug report #781512,
regarding puppet: service enable does not work on sysvinit with new initscripts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
781512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781512
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Apollon Oikonomopoulos <apoikos at debian.org>
Subject: puppet: service enable does not work on sysvinit with new initscripts
Date: Mon, 30 Mar 2015 12:39:13 +0300
Size: 3560
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150330/9276bef5/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Apollon Oikonomopoulos <apoikos at debian.org>
Subject: Bug#781512: fixed in puppet 3.7.2-4
Date: Mon, 30 Mar 2015 11:48:47 +0000
Size: 7559
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150330/9276bef5/attachment-0003.mht>

From bts-link-upstream at lists.alioth.debian.org  Mon Mar 30 16:29:00 2015
From: bts-link-upstream at lists.alioth.debian.org (bts-link-upstream at lists.alioth.debian.org)
Date: Mon, 30 Mar 2015 16:29:00 -0000
Subject: [Pkg-puppet-devel] [bts-link] source package puppet
Message-ID: <20150330162847.32166.21562.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package puppet
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user bts-link-upstream at lists.alioth.debian.org

# remote status report for #769621 (http://bugs.debian.org/769621)
# Bug title: puppet: USR1 fails to trigger agent run
#  * https://tickets.puppetlabs.com/browse/PUP-1635
#  * remote status changed: Resolved -> Closed
#  * remote resolution changed: Fixed -> Done
usertags 769621 - status-Resolved resolution-Fixed
usertags 769621 + status-Closed resolution-Done

thanks


From inbox at hms-test.info  Tue Mar 31 12:19:54 2015
From: inbox at hms-test.info (HMS-test.no)
Date: Tue, 31 Mar 2015 12:19:54 +0000
Subject: [Pkg-puppet-devel] =?utf-8?q?Ta_HMS-testen_p=C3=A5_nettet?=
Message-ID: <84a3e8efcced059c7edec061a5e09877@hms-test.info>

Your email client cannot read this email.
To view it online, please go here:
http://hms-test.info/iem/display.php?M=473413&C=b4fe84a966700035a83d8d011d779dcd&S=14&L=1&N=5


To stop receiving these
emails:http://hms-test.info/iem/unsubscribe.php?M=473413&C=b4fe84a966700035a83d8d011d779dcd&L=1&N=14
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20150331/ab278dbd/attachment.html>